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/attac-t/the-foundryWrote 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/attac-t/the-foundry/author)<a href="https://agentmods.dev/agents/attac-t/the-foundry/author"><img src="https://agentmods.dev/badge/agents/attac-t/the-foundry/author/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/attac-t/the-foundry/author"><img src="https://agentmods.dev/badge/agents/attac-t/the-foundry/author.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.00021 | $0.00802 |
| Opus 5.5 | $0.00008 | $0.00321 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
author 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 85 lines · 21 tokens per session scan A 677efd9d714b
author is an agent published in the GitHub repository attac-t/the-foundry (1 stars, last pushed 3d ago), with no licence file. It adds 21 tokens to every session and 802 once invoked, about $0.0001 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-03.
Other agents, from other repositories
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
verifier
Cheap re-check after a tests-only fix round — re-runs each test-gap finding's mutation and confirms the new tests go red. Used instead of a full spec re-review. Dispatched by the orchestrate-issues skill only; never self-initiate.
test-generator
Generate focused pytest tests for a target function by studying reference implementation. Use during test curation (phase 2) after test discovery.
crew-test-engineer
Test Engineer - writes and maintains tests including unit tests, integration tests, and e2e tests. Handles TDD workflow, test strategy, and coverage analysis.
wiki-dev-qa-functional
QA — Functional & Test engineer for the claude-wiki-pages development team. Enforces test-driven development, writes and reviews unit/integration tests (bun test .test.ts and Bats .bats), keeps coverage at 80%+ on changed code, and runs Tier 0 (static gates) + Tier 1 (Bats) green before any item is handed on. Owns…
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…