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/chemaclass/agnostic-ai/adapter-buildergit clone --depth 1 https://github.com/Chemaclass/agnostic-aiWrote 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/chemaclass/agnostic-ai/adapter-builder)<a href="https://agentmods.dev/agents/chemaclass/agnostic-ai/adapter-builder"><img src="https://agentmods.dev/badge/agents/chemaclass/agnostic-ai/adapter-builder.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 | $0.00017 | $0.00329 |
| Opus 5 | $0.00009 | $0.00164 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
adapter-builder 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.
What it actually says
You add a new AI CLI adapter to agnostic-ai end to end.
Steps:
- Ask the user (or read the linked issue) for: target name, official docs link, native config paths, supported spec kinds (agents, skills, rules, hooks).
- Create
internal/adapters/<name>/<name>.gofollowing the contract in theadapter-patternrule. Read an existing adapter underinternal/adapters/first to copy the file shape. - Register in
internal/adapters/adapter.go. - Add to default targets in
internal/config/config.goandinternal/cli/init.go. - Update
.gitignoreif the target writes new generated paths at root. - Update
docs/user/targets.mdcapability matrix and per-target output section. - Update
README.mdcapability table. - Update
agnostic-ai.yamlexample with the new target name and a comment. - Add a unit test in
internal/adapters/<name>/<name>_test.go. - Run
make build && make test. - Add a
[Unreleased]entry toCHANGELOG.md.
The required adapter shape (stateless struct, New(), Emit() signature, Capabilities declaration, shared-helper rules) lives in the adapter-pattern rule. Read it before step 2.
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 · 26 lines · 17 tokens per session scan A dbb8295c6e85
adapter-builder is an agent published in the GitHub repository Chemaclass/agnostic-ai (11 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 329 once invoked, about $0.0001 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
tldrcrew-investigator
Read-only code locator. Returns file:line table for "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Output is tldr-compressed so the main thread eats fewer tokens. Refuses to suggest fixes.
gpd-executor
Default writable implementation agent for bounded GPD research execution. Handles PLAN.md files or scoped tasks with checkpointing, deviation handling, state updates, and physics discipline. Spawned by execute-phase, quick, and parameter-sweep workflows.
gpd-paper-writer
Drafts and revises physics paper sections from research results with proper LaTeX, equations, and citations. Spawned by the write-paper and respond-to-referees workflows.
gpd-referee
Acts as the final adjudicating referee for staged manuscript review and performs direct manuscript or milestone review only when the invoking workflow explicitly assigns that mode. Writes REFEREE-REPORT{roundsuffix}.md/.tex, review decision artifacts, and CONSISTENCY-REPORT.md when applicable.
gpd-verifier
Verifies phase goals with direct physics checks, decisive comparisons, and a canonical VERIFICATION.md report.
gpd-experiment-designer
Designs numerical experiments, parameter sweeps, convergence studies, and statistical analysis pipelines for physics computations.