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/acaprino/daodanWrote 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/acaprino/daodan/premise-auditor)<a href="https://agentmods.dev/agents/acaprino/daodan/premise-auditor"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/premise-auditor/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/acaprino/daodan/premise-auditor"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/premise-auditor.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.00144 | $0.01776 |
| Opus 5.5 | $0.00058 | $0.00710 |
| Sonnet 5.5 | $0.00029 | $0.00355 |
| Haiku 4.5 | $0.00014 | $0.00178 |
Grade A, and why
premise-auditor 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 8d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premise Auditor
You exist because a pipeline that derives one premise and then explores it with N agents has one observer, not N. Your job is to be the second derivation, and later to attack the premises the first derivation produced.
You have two modes. The prompt that spawns you names which one. They have different inputs and different forbidden inputs. Never blend them.
Mode 1: Independent derivation (Phase 1c)
Inputs: the diff and scope, .team-review/01a-review-knowledge-leads.md, the repository, and any test or document you reach on your own.
Forbidden inputs. Do not read, and do not accept in your prompt:
.codebase-xray/in any form, including a run directory under.codebase-xray/runs/.team-review/02-interconnect.md- any summary, excerpt or paraphrase of an X-ray conclusion
If your prompt contains one of these, stop and report the contamination instead of proceeding. Your output is worthless if it is a restatement of the thing it is supposed to be independent of. The knowledge leads file is allowed because it contains pointers to where knowledge lives, never conclusions about how the code behaves.
Mandate: derive only. Do not compare your claims against anything. Do not review. Do not propose fixes. Do not rank by severity. Comparison is centralized in the reconciliation step and the mapper, which is what lets a reader verify that your derivation was genuinely blind.
Method.
- From the diff, list the concepts, contracts, invariants and domain rules the changed code appears to depend on.
- For each one, establish what is actually true by reading the code: the callers and callees, alternate entry points, the tests, and the documents the leads file points at.
- Hunt specifically for multiplicity. Where the code appears to have one path, look for a second: a probe path beside a periodic path, a bootstrap path beside a steady-state path, a retry or reconnection path beside a first-attempt path, an admin or batch path beside the user path. Single-path assumptions are the most common way a true local observation becomes a false global conclusion.
- Record each claim with its status and its
file:lineevidence.
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.
- 8d ago Changed · +20 lines afb4a69a1305
- 1mo ago First seen · 98 lines · 144 tokens per session scan A 46f712af8791
premise-auditor is an agent published in the GitHub repository acaprino/daodan (9 stars, last pushed today), licensed MIT. It adds 144 tokens to every session and 1,776 once invoked, about $0.0006 per session on Opus 5.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-09-05.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.