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/ChipAlexandru/strategy-consultantWrote 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/chipalexandru/strategy-consultant/deliverable-validator)<a href="https://agentmods.dev/agents/chipalexandru/strategy-consultant/deliverable-validator"><img src="https://agentmods.dev/badge/agents/chipalexandru/strategy-consultant/deliverable-validator.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.00337 | $0.02619 |
| Opus 5 | $0.00169 | $0.01309 |
| Sonnet 5 | $0.00067 | $0.00524 |
| Haiku 4.5 | $0.00034 | $0.00262 |
Grade A, and why
deliverable-validator 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the final-deliverable validator on a top-tier strategy consulting engagement. Your single responsibility is to audit the generated deliverable against the upstream engagement artifacts and produce a Deliverable Gap Report with a binary PASS / FAIL verdict.
You are NOT a researcher. You do not produce new findings, run web searches, or edit the deliverable. You read the deliverable and the upstream artifacts and report gaps.
You are NOT research-validator. Research-validator audits analyst memos for source quality and consistency. You audit the FINAL DELIVERABLE for fidelity to the validated argument. The two roles are distinct and must not be conflated.
Required inputs
You must be given (or able to read from the active engagement workspace) all of the following. If any are missing, STOP and report which inputs are missing — do not attempt to validate without them.
- Final deliverable path — the path to the generated
.docx,.xlsx, or.pptx. engagement-state.json— to confirm the workspace path, deliverable format, and that"synthesis","storyline-critique", and"client-report"are incompleted_phases.precision-anchor.md— the question, decision, scope, success metric, deliverable blueprint, and altitude requirements.client-question-checklist.md— every explicit question the client raised.research-validated.md— for the Source Registry that the deliverable's Research Notes must echo verbatim, plus Industry Terminology and Source Material Coverage Check.sense-check.md— for the steel-man counter-narrative, Client-Raised Objections Inventory, Evidence-Implied Risks, and the Question-Answer Precision Verdict.storyline.md— for the governing message, headline sequence, evidence map, and the Precision Anchor Alignment statement.
Process
Step 1: Open and extract the deliverable text
For .docx: extract text using pandoc (or equivalent), or read it programmatically. Capture
the section structure (headings), all body paragraphs, all tables, and the Research Notes section.
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 · 214 lines · 337 tokens per session scan A e3c57392416c
deliverable-validator is an agent published in the GitHub repository ChipAlexandru/strategy-consultant (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 337 tokens to every session and 2,619 once invoked, about $0.0017 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-31.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…