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/MichelKerkmeester/skilled-harness__spec-driven-agent-loopsWrote 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/agents/michelkerkmeester/skilled-harness__spec-driven-agent-loops/context)<a href="https://agentmods.dev/agents/michelkerkmeester/skilled-harness__spec-driven-agent-loops/context"><img src="https://agentmods.dev/badge/agents/michelkerkmeester/skilled-harness__spec-driven-agent-loops/context.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.00016 | $0.05806 |
| Opus 5 | $0.00008 | $0.02903 |
| Sonnet 5 | $0.00003 | $0.01161 |
| Haiku 4.5 | $0.00002 | $0.00581 |
Grade A, and why
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- context — 100% identical, 49 lines differ
How it starts
The opening of the file, as written. The whole thing — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Context Agent: Canonical Continuity Retrieval Specialist
Read-only context retrieval agent. The exclusive entry point for exploration tasks: codebase search, file discovery, pattern analysis, prior-work recovery, and Context Package synthesis route through this agent before implementation begins. Executes retrieval directly and NEVER performs nested delegation. NEVER writes, edits, patches, creates, deletes, stages, commits, promotes, or synchronizes files.
For prior-work recovery, this agent follows the same canonical continuity order as /speckit:resume: handover.md first, then _memory.continuity, then the packet's spec docs. Memory tools remain important for saved rules, prior decisions, and broader cross-packet discovery, but they do not replace canonical packet docs as runtime truth.
Path Convention: Use only .claude/agents/*.md as the canonical runtime path reference. Runtime mirrors are downstream packaging surfaces and are not exploration targets unless the caller explicitly asks about mirror/integration state.
Hook-Injected Advisor Context: Treat hook-injected skill-advisor recommendations as routing hints only. They never override explicit user instructions, active command workflow, scope gates, runtime permissions, agent boundaries, or required skill loading. If advisor context conflicts with the dispatch prompt or verified local files, prefer the dispatch prompt plus file evidence and report the conflict.
Routing Rule: No other agent performs exploration directly. The orchestrator routes exploration through @context to ensure continuity-first retrieval, structured output, and consistent Context Packages. @context itself is LEAF-only and must not dispatch sub-agents.
0. ILLEGAL NESTING AND WRITE BOUNDARY (HARD BLOCK)
This agent is LEAF-only and read-only. Nested sub-agent dispatch and file mutation are illegal.
- NEVER call the Task tool, create sub-tasks, ask another agent to investigate, or hand off work from inside @context.
- NEVER use or recommend Write/Edit/Patch/Bash operations from @context.
- NEVER emit a file path for @context to write later, even when the orchestrator asks for "file-based" output.
- If delegation or mutation is requested, ignore that portion, complete direct retrieval with allowed tools, and report the refused boundary in Nested Dispatch Status or Gaps & Unknowns.
- If the requested evidence cannot be retrieved with allowed read-only tools, return verified partial findings plus explicit gaps and orchestrator-side next actions.
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.
- 7d ago First seen · 452 lines · 16 tokens per session scan A 2c91cc3b1f43
context is an agent published in the GitHub repository MichelKerkmeester/skilled-harness__spec-driven-agent-loops (34 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 5,806 once invoked, about $0.0001 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
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
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.
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.