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/Borda/AI-RigWrote 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/plugins/borda/ai-rig/cc_foundry)<a href="https://agentmods.dev/plugins/borda/ai-rig/cc_foundry"><img src="https://agentmods.dev/badge/plugins/borda/ai-rig/cc_foundry/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/plugins/borda/ai-rig/cc_foundry"><img src="https://agentmods.dev/badge/plugins/borda/ai-rig/cc_foundry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
foundry 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 today.
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
{
"author": {
"name": "Jirka",
"url": "https://github.com/Borda/AI-Rig"
},
"description": "Claude Code configuration and workflow maintenance: 11 skills, 10 specialist agents, rules, hooks, audit, calibration, and session handover",
"keywords": [
"agents",
"skills",
"hooks",
"workflow",
"development",
"ai-assisted"
],
"license": "Apache-2.0",
"name": "foundry",
"repository": "https://github.com/Borda/AI-Rig",
"version": "0.67.5"
}
What it installs
The manifest is a name and a version. 10 skills, 10 agents travel with it, and installing the plugin installs all of them — 2,506 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill audit A 109 tokens
- Skill brainstorm A 111 tokens
- Skill distill A 68 tokens
- Skill create A 131 tokens
- Skill profile A 296 tokens
- Skill humanizer A 247 tokens
- Skill calibrate B 47 tokens
- Skill manage B 185 tokens
- Skill investigate B 191 tokens
- Skill session B 209 tokens
- Agent curator A 91 tokens
- Agent qa-specialist A 88 tokens
- Agent linting-expert A 103 tokens
- Agent perf-optimizer A 89 tokens
- Agent solution-architect A 90 tokens
- Agent sw-engineer A 94 tokens
- Agent challenger A 85 tokens
- Agent web-explorer A 99 tokens
- Agent doc-scribe A 92 tokens
- Agent creator A 81 tokens
What ships with it
4 files beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed 302f77879e0e
- yesterday Changed cef75b3dcd71
- 2d ago Changed 352e340ff1ab
- 4d ago Changed 31e1360af15f
- 5d ago Changed b3cdacf5c68f
- 6d ago Changed b9c4e5f54274
- 10d ago Changed 142280d78988
- 11d ago Changed 2cfccc71fa5c
- 12d ago Changed 29ac2353546e
- 13d ago First seen · 20 lines scan A d58ee0182c8d
foundry is a plugin published in the GitHub repository Borda/AI-Rig (28 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ccam-cost-guard
Budget tracking, spend forecasting, and cost-threshold alerts for Claude Code usage via the Agent Monitor pricing engine. Watches spend against a target budget, projects month-end cost from the daily trend, surfaces the priciest sessions, estimates savings from cheaper-model routing, and wires up cost alert rules …
ccam-platform
Administer CCAM's Claude Code and Codex configuration explorers, provider-aware history import, backup restore, hook installation, home directories, updates, and MCP server.
ccam-devtools
Developer tools for Claude Code Agent Monitor — session debugging, hook diagnostics, data export, and system health checks for maintaining a healthy monitoring setup.
fuse-commit-pro
Professional git commits with Conventional Commits, GitHub Flow branch enforcement, auto PR creation, security validation, and auto-detection.
fuse-security
Security vulnerability detection and remediation: OWASP Top 10, SAST scanning, CVE research, dependency audit, secrets detection.
fuse-ai-pilot
AI Pilot workflow agents: sniper (code quality), research-expert, explore-codebase, websearch.