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/ldilov/harness-forgeWrote 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/ldilov/harness-forge/documentation-lookup)<a href="https://agentmods.dev/agents/ldilov/harness-forge/documentation-lookup"><img src="https://agentmods.dev/badge/agents/ldilov/harness-forge/documentation-lookup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ldilov/harness-forge/documentation-lookup"><img src="https://agentmods.dev/badge/agents/ldilov/harness-forge/documentation-lookup.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00010 |
| Opus 5 | $0.00000 | $0.00005 |
| Sonnet 5 | $0.00000 | $0.00002 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
documentation-lookup 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 5d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 5d ago First seen · 4 lines · 0 tokens per session scan A dc613a2fee12
documentation-lookup is an agent published in the GitHub repository ldilov/harness-forge (4 stars, last pushed 3mo ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 10 tokens. 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-09-03.
Other agents, from other repositories
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
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.
spec-reviewer
Reviews specifications for testability, completeness, and ambiguity. Invoke before approving a spec, when a spec is revised, or when acceptance criteria need to be stress-tested for measurability. Returns findings with severity and a verdict of Approve or Revise.
quality-scanner
Evaluates code quality with zero knowledge of intent — correctness, safety, maintainability, testing, and over-engineering. Receives diff + code only; never reads plans, specs, or designs. Intent-blindness is the point: plan-aware reviewers forgive code that 'does what was asked', this one doesn't. Dispatched in…
drift-detector
Detects drift between a plan and the code being built: missing work (plan → no code), scope creep (code → no plan), and approach drift (code solves the task differently than the plan prescribed). Receives diff + plan + phase doc + prior debriefs only — never specs, designs, or code-quality context. Dispatched in…
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.