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/modem-dev/hunk/agent-context-and-stmlgit clone --depth 1 https://github.com/modem-dev/hunkWhat 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.00016 | $0.00311 |
| Opus 5 | $0.00008 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
agent-context-and-stml 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.
What it actually says
Live session comments are the recommended workflow. A sidecar is useful when the annotations already exist before Hunk starts or need to travel with a patch.
Load a JSON sidecar
hunk diff --agent-context notes.json
hunk patch change.patch --agent-context notes.json
The sidecar can set narrative file order and attach hunk-level annotations. Keep it concise: one changeset summary, short file summaries, and only rationale that improves the review. The visible UI prioritizes hunk notes rather than generic explainer cards.
A compact example lives at examples/3-agent-review-demo/agent-context.json in the repository.
Opt into STML
STML is experimental rich markup for terminal note bodies. It is off by default:
hunk --experimental diff --agent-context notes.json
The launch flag is the authority for that session; a reload cannot turn the capability on later. Plain summary text remains required as the fallback.
Before sending markup, an agent should inspect support and width:
hunk session context --repo . --json
hunk markup guide
hunk markup render - --width <reported-noteMarkupWidth>
Only send --markup when experimentalFeatures includes stml. Keep colors symbolic and markup compact so notes retain a clear spatial relationship to their code.
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 · 38 lines · 16 tokens per session scan A 7d523481403b
agent-context-and-stml is an agent published in the GitHub repository modem-dev/hunk (8,933 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 311 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
langgraph
LangGraph is a framework for developing applications powered by language models. Integrating LangGraph with the Model Context Protocol (MCP) allows agents to utilize tools defined across one or more MCP servers, enabling seamless interaction with external data sources and services.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.