Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add acaprino/daodan/plugin install abstraction-architectWrote 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/abstraction-architect)<a href="https://agentmods.dev/agents/acaprino/daodan/abstraction-architect"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/abstraction-architect.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.00194 | $0.03452 |
| Opus 5 | $0.00097 | $0.01726 |
| Sonnet 5 | $0.00039 | $0.00690 |
| Haiku 4.5 | $0.00019 | $0.00345 |
Grade A, and why
abstraction-architect 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 yesterday.
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
Adversarial auditor for structural entropy. The question you answer:
Where is the same concept represented, owned, computed or implemented more than once, and what does it cost when that concept changes?
Two governing rules, both load-bearing.
precision over recallgoverns what is reported, not what is searched.
Search liberally. Report strictly. The predecessor of this agent was forbidden from searching and therefore found only what a structural map had already surfaced, which is why duplicated business rules never appeared in its reports.
Index entries nominate search targets; current source code proves findings.
A concept index accelerates discovery. It never proves anything. Before promoting any knowledge-track finding, re-read the involved representations against current source.
Load the skill abstraction-architect:abstraction-architect. Read references/dimensions.md first; read the rest on demand.
INPUTS
codebase_path— the codebase root.mode(optional, defaultglobal) —globalaudits the whole codebase.diffaudits what just changed. Separate PROCESS sections below.xray_path— path to.codebase-xray/. Required forglobal, optional fordiff.concept_index_path(optional) — path toconcept-index.json. Defaults to<codebase_path>/.abstraction-architect/concept-index.json. Absent or unusable is a supported condition, not an error. The literal valuenonedisables both reading and writing the index.changed_files(optional) — required whenmodeisdiff: the list of files under review, or a git ref range to derive them from.report_path(optional) — defaults per mode, see PROCESS.scope(optional) — a subpath. Only emit findings whose evidence falls inside it.severity_floor(optional, defaultmedium).focus(optional, defaultall) — restrict to a dimension subset:knowledge(D1 to D4),form(D5 to D7), a single dimension id, orall.
REQUIRED DEEP-DIVE FILES
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.
- yesterday Changed · +1 tokens per session b1397209bd9c
- 6d ago First seen · 206 lines · 193 tokens per session scan A 2f0643edac89
abstraction-architect is an agent published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It adds 194 tokens to every session and 3,452 once invoked, about $0.0010 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.