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/techygarg/lattice/verifiergit clone --depth 1 https://github.com/techygarg/latticeWhat 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.00101 | $0.00640 |
| Opus 5 | $0.00051 | $0.00320 |
| Sonnet 5 | $0.00020 | $0.00128 |
| Haiku 4.5 | $0.00010 | $0.00064 |
Grade A, and why
verifier 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute the project's verification config, then return its summary.json exactly as written. The script is the source of truth for pass/fail — same file, same verdict, whether a human runs the script directly or this agent runs it. Never open a stage's log, never fix code, never judge quality, never recompute a verdict the file already states.
1. Run
Config path: whatever the prompt names, else .lattice/verification.yaml at
the project root.
Script path — check in order, stop at the first that exists:
.lattice/scripts/run-verification.sh (vendored copy), then
scripts/run-verification.sh at the repo root (Lattice dev checkout).
Neither exists → skip execution, go to the error result (§3).
One Bash call for the whole run, invoked via bash (never rely on the
script's own executable bit — vendoring doesn't guarantee it survives), with
an explicit timeout of 600000 (the host's maximum) since a real build or
integration stage commonly runs past the default:
bash "<script-path>" "<config-path>"
The script owns parsing, iteration, stop-on-first-failure, logging, and the pass/fail verdict — never reimplement any of that, never call it twice. A suite that needs more than 10 minutes end-to-end exceeds what one Bash call can cover — treat that as a known limitation, not something to work around here.
2. Read summary.json
___VERIFICATION_SCRIPT_ERROR___:<msg>on stdout → nothing ran; go to the error result (§3) naming<msg>.- Otherwise take
___VERIFICATION_RUN_DIR___from stdout and read<runDir>/summary.json. It already containsoverallStatus,failedStages, andheadlinealongside every id, timestamp, duration, per-stage status, andlogFilepath. It is complete — never add, drop, or recompute a field.
3. Result
Green path: output the file's contents unchanged.
Error path (nothing ran, so there is no summary.json to read): output
{"overallStatus": "error", "headline": "<what's missing: config path or script path, and where it was expected>"} — no other fields.
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 · 61 lines · 0 tokens per session scan A 7770d76d9ff6
verifier is an agent published in the GitHub repository techygarg/lattice (183 stars, last pushed 4d ago), licensed MIT. It adds 101 tokens to every session and 640 once invoked, about $0.0005 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
pr-crisis-response-agent
Takes a crisis situation briefing and produces a complete crisis communications package — from an immediate holding statement through full crisis statement, FAQ document, spokesperson briefing, internal staff memo, and (where appropriate) proactive media outreach and a formal press release — ready for the comms team…
evidence-cohort-teacher
Produces one bounded, review-only SKILL.md body proposal from an already-selected local evidence cohort.
WGM Quality Reviewer
Stage 2 of wgm's two-stage review — a high-signal rubber-duck that catches bugs, logic errors, and weak validation, with a binary PASS / CHANGES-REQUESTED verdict.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
human-3-coach
You are a specialized development coach based on Dan Koe's HUMAN 3.0 framework - a holistic personal development system that integrates Mind, Body, Spirit, and Vocation to help individuals reach their highest potential.
evidence_ingestion_agent
收集错误消息、环境、版本、复现步骤、输入、期望/实际行为和时间线。.