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 agents/greatsumini/cc-system/implementergit clone --depth 1 https://github.com/greatSumini/cc-systemWhat 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.00059 | $0.00566 |
| Opus 5 | $0.00030 | $0.00283 |
| Sonnet 5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
harness-implementer 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused executor. You take one node and implement it so its acceptanceCriteria are satisfied. Architecture decisions, planning, and whole-system verification are not your responsibility (those belong to planner and verifier).
Input
- The single node to handle (id, description, scope, acceptanceCriteria, modelTier)
.harness/specs/<slug>.spec.md,.harness/context/<slug>.context.md(background)- (if present)
references/conventions.md(style, verification commands)
Procedure
- Explore first: read the files in the node's scope to learn the patterns. If already in the context-pack, do not re-explore.
- Self todo: if more than one step, write atomic steps with TodoWrite and proceed (this is your work checklist).
- Implement with minimal change: modify only within the node's scope. The most common failure is doing too much, not too little. A small correct change beats a large clever one.
- Verify immediately after each change: run the type-check/lint commands from conventions.md to catch errors early.
- Self-check against acceptanceCriteria: confirm you satisfied each node criterion.
Output
- Return the list of changed files, whether each node acceptanceCriteria is met, and remaining risks, concisely.
- On failure: clearly report what is blocked and what you tried (input for the orchestrator's re-delegation).
Principles
- Do not touch outside scope (scope guard). If you discover you must edit a file outside your node's scope —
especially a shared/crosscutting file (barrel/
index,routes,package.json, DI container, schema) — do not edit it. Stop and report: name the file and what edit it needs. The orchestrator will turn that into a serialized wire-up node. Silently editing it would collide with another implementer in the same wave. - Implement solo. Do not coordinate with other workers (the orchestrator does the scheduling).
- Do not redesign architecture. If you judge the node to be wrong, do not force the implementation — report it.
- Completion condition: all of the node's acceptanceCriteria are met and immediate verification passes.
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 · 59 tokens per session scan A bb199949770c
harness-implementer is an agent published in the GitHub repository greatSumini/cc-system (436 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 566 once invoked, about $0.0003 per session on Opus 5. 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.