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-annotation)<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/new-annotation"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/new-annotation.svg" alt="Measured on agentmods" 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.00126 |
| Opus 5 | $0.00000 | $0.00063 |
| Sonnet 5 | $0.00000 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
new-annotation 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 3d 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
Add a new annotation to the framework. Requires:
- Define the annotation in
modules/annotations/with proper @Target, @Retention(RUNTIME), and Javadoc. - Update the processor in
modules/processor/to recognize and handle the new annotation. - Add compile-testing tests verifying correct generation and error cases.
- Update the demo app to exercise the new annotation.
- Update
docs/annotation-guide.mdwith usage examples.
Ensure the annotations module remains zero-dependency. The new annotation must not break existing processor behavior — run full test suite to verify.
$ARGUMENTS
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.
- 3d ago First seen · 11 lines · 0 tokens per session scan A 532fdf042bb1
new-annotation is a command published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 126 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
benchmark
Design and coordinate a reproducible Java performance test.
python-scaffold
Generate a fresh project skeleton, tests and lint config included. TRIGGER WHEN: the user asks to start a new Python project, bootstrap FastAPI/Django/CLI/library structure, or set up uv+pytest+ruff from scratch. DO NOT TRIGGER WHEN: adding to an existing project (use python-engineer).
golang-test-review
Use when reviewing Go test code (new or changed test.go files, test harnesses, fixtures, or test tooling) for a Go-test-expert pass — behavior-over-surface, determinism, parallel-safety, build-tag correctness, and harness reuse. Complements the general code-reviewer with test-specific rigor.
comprehensive-unit-testing-with-pytest
Aims for high test coverage using pytest, testing both common and edge cases.
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.