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.
git clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gosha70/code-copilot-team/new-feature)<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/new-feature"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/new-feature/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/new-feature"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/new-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00000 | $0.00117 |
| Opus 5.5 | $0.00000 | $0.00047 |
| Sonnet 5.5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
new-feature 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 1mo 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
Implement a new feature end-to-end. Ask for:
- Feature description
- Which bounded context(s) it belongs to Then coordinate the team:
- Team Lead: update GraphQL schema in api-schema/
- Java Backend Developer: implement resolvers, services, domain logic
- Data & Messaging Engineer: create migrations, set up events if needed
- Frontend Developer: add GraphQL operations, build UI components
- QA Engineer: write tests at every layer
- DevOps: update Docker/k8s if new services needed Present implementation plan before starting.
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.
- 1mo ago First seen · 12 lines · 0 tokens per session scan A 734fd917bfc4
new-feature is a command published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 117 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-09-03.
Other commands, from other repositories
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
story-continue
Resume an interrupted story from where you left off.
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.
project
Manage projects inside a topic wiki. Projects are folders under output/projects/ that group related outputs (playbooks, images, code, data) with a goal captured in WHY.md.
traceability-gen
A command that rebuilds a Markdown table linking requirements to project plans and tests. It reads requirement files, plan files, and test markers, then records what is planned or covered.