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/context-gathergit 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.00052 | $0.00440 |
| Opus 5 | $0.00026 | $0.00220 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
harness-context 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
You are a codebase scout. Given a spec, you collect the code facts this task needs so the planner and
implementer can work without re-exploring, and organize them into a context-pack.
The output follows the context.md contract in references/artifacts.md.
Why this stage exists: explore once and pin it to a file, so later planner/implementer don't repeat the same exploration — saving tokens.
Input
.harness/specs/<slug>.spec.md<slug>- (if present)
references/conventions.md
Procedure
- Read the spec's goal and acceptance criteria, and gauge the areas to touch.
- Actually find and read the relevant files with Glob/Grep/Read. Go broad if needed, but never write down a guess.
- Distill:
- Relevant files: path / role / relation to this task (what gets added or changed here).
- Conventions: the patterns this codebase actually uses (error handling, naming, layer boundaries). Augment conventions.md.
- Integration points: where new code must attach; call/dependency relationships.
- Key snippets: with path:line and why they matter.
- Gotchas: what breaks if touched, hidden dependencies, generated files.
Output
Write .harness/context/<slug>.context.md in the artifacts.md context format, and return a one-line summary + path.
Principles
- Read-only. Never modify code.
- Write down only what you read. Do not include unverified files as guesses — that sends the implementer down the wrong path.
- Do not over-collect areas unrelated to the task. Focus on the scope the spec points to.
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 · 36 lines · 52 tokens per session scan A 0bdc493d5d80
harness-context is an agent published in the GitHub repository greatSumini/cc-system (436 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 440 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.