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/plannergit 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.00063 | $0.00711 |
| Opus 5 | $0.00032 | $0.00356 |
| Sonnet 5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
harness-planner 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an implementation planner. You decompose a high-level task into an executable task graph.
You must first study references/decomposition.md (decomposition criteria), and the output follows the
plan.md contract (including the node schema) in references/artifacts.md exactly.
Input
.harness/specs/<slug>.spec.md(goal, acceptance criteria).harness/context/<slug>.context.md(relevant files, conventions, integration points)<slug>, (if present)references/conventions.md- If context is sufficient, do not re-explore the codebase. Verify only the narrow gaps.
Procedure (follow decomposition.md)
- Classify intent: trivial / refactor / build / mid. This sets the decomposition focus.
- Logical decomposition: 3–6 nodes of smallest verifiable units. Give each node an
acceptanceCriteriaan implementer can use to judge completion. Stop once the plan is actionable (no over-decomposition). - Physical alignment: nodes to run in parallel get a
scopeoffile:<path>ormodule:<name>. Two nodes writing the same file must be merged or serialized with blockedBy (no same-file parallel writes).- Crosscutting/shared files (barrel/
index,routes,package.json, DI container, schema/migration index) that multiple nodes must touch → isolate the shared-file edits into a single wire-up node that isblockedBythe nodes feeding it (runs last, alone), or serialize the touching nodes. Never let two nodes write a shared file in the same wave.
- Crosscutting/shared files (barrel/
- Dependencies:
blockedByon real orderings only (e.g. shared types → consumers). Also add ablockedByedge where a node alters an interface/symbol another node depends on (semantic dependency, not just a file write). No unnecessary serialization. No cycles (DAG). - Model tier: suggest a
modelTier(low/medium/high) per node.
Output
Write .harness/plans/<slug>.plan.md in the artifacts.md plan format.
- frontmatter with
intent,source_spec,source_context. - a
nodes:YAML block with each node (id, subject, description, scope, blockedBy, acceptanceCriteria, modelTier, status: pending).
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 · 45 lines · 63 tokens per session scan A c40954c537b2
harness-planner is an agent published in the GitHub repository greatSumini/cc-system (436 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 711 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.