Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/gosha70/code-copilot-team/shapegit clone --depth 1 https://github.com/gosha70/code-copilot-teamWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00379 |
| Opus 5 | $0.00000 | $0.00189 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
shape scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Shape a rough idea into a Shape-Up pitch via the pitch-shaper agent.
Usage: /shape <topic>
Steps
1. Parse arguments
The <topic> is the rough idea — a one-line description (e.g. add streaming responses to the chat API). If absent, ask the user for one.
2. Invoke pitch-shaper
Use the Agent tool with subagent_type: pitch-shaper. Pass the topic and any additional context the user has volunteered.
The pitch-shaper will:
- Pick the next
NNNN-slugpitch id underspecs/pitches/ - Ask clarifying questions (appetite, problem, solution shape, no-gos, circuit breaker)
- Decompose into 3–7 scopes
- Write
specs/pitches/<id>/pitch.mdfrom~/.claude/templates/sdd/pitch-template.md - Set
bet_status: shaped - Validate via
~/.claude/templates/sdd/validate-pitch.sh
3. Report to user
Once pitch-shaper returns, print:
- The new pitch path
- Frontmatter summary (id, appetite, scope count, circuit breaker)
- Validator confirmation
- Next step: "Run
/bet <pitch-id>to lock this as a bet for the next cycle, or refine via direct edits."
Notes
- This command does not lock the pitch as a bet.
bet_status: shapedmeans "ready for the betting table" — not yet committed. - A pitch can sit in
shapedindefinitely. Only/betadvances tobet_status: bet. - Re-running
/shapefor the same topic produces a NEW pitch with a new id — it does not overwrite. Edit the existing pitch directly if you want to refine.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 36 lines · 0 tokens per session scan A a6167d6bc2da
shape is a command published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 379 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.