Skip to content

feat(distribution): add Gittensory custom agent profiles #276

Description

@JSONbored

Parent roadmap: #127
Parent phase: #238

Goal

Add Gittensory custom agent profiles so supported coding-agent environments can use the MCP package with the right instructions and safety boundaries out of the box.

Requirements

  • Add profiles for miner planner, maintainer queue triage, and repo-owner intake.
  • Wire profiles to Gittensory MCP usage where supported.
  • Keep all profiles human-approved: they may plan, explain, draft, and prepare packets, but they must not autonomously open PRs, post comments, close issues, label, merge, or publish public GitHub output.
  • Document installation and expected boundaries in the launch/docs path.

Acceptance criteria

  • Profiles are concise, distinct, and usable by supported clients.
  • Each profile includes explicit public/private safety language.
  • Profiles do not ask for wallet, hotkey, coldkey, private keys, or tokens.
  • Docs explain how to install and when not to use them.

Validation expected

  • Static validation for profile files if added.
  • Docs/link check where applicable.
  • npm run test:ci if code/config is touched.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions