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.
/plugin marketplace add lukasrepublic/agentic-foundrynpx agentmods add plugins/lukasrepublic/agentic-foundry/marketplacegit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryGrade A, and why
agentic-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 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.
What it actually says
{
"name": "agentic-foundry",
"description": "Governed, spec-driven delivery for agent-built software: operator-authorized acceptance contracts, an honestly-tiered merge floor on your own branch protection + CI, deploy-once certification, and a citation-graph MCP.",
"owner": {
"name": "lukasrepublic"
},
"plugins": [
{
"name": "foundry",
"description": "Governed, spec-driven delivery for agent-built software (skills, acceptance contracts, honest merge-floor discipline, citation-graph MCP).",
"source": {
"source": "github",
"repo": "lukasrepublic/agentic-foundry",
"ref": "v1.6.0",
"sha": "0b333f77ffb2cf4051b022158c49c5bb9c291a49"
},
"version": "1.6.0"
}
]
}
What ships with it
1 file beside marketplace.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.
- yesterday First seen · 21 lines scan A 9e8ef3bed13b
agentic-foundry is a plugin published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed yesterday), licensed MIT. 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-31.
Other plugins, from other repositories
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
wt-local
Local marketplace populated by wta.
antimicrobial-resistance-scientist
Reasons from MIC distributions, ECOFFs, and phenotype–genotype concordance through EUCAST/CLSI AST, CARD/RGI and AMRFinderPlus resistomes, GLASS/WHONET/NARMS surveillance, carbapenemase/ESBL/MRSA mechanism panels, and heteroresistance PAP while treating breakpoint mixing, genotype-without-phenotype overclaim…
moraine
Claude Code plugin for Moraine MCP session search, realtime agent awareness, and sanitized bug reports.
ainb-hooks
Emit every safely observable Claude Code lifecycle event into Hangar's durable provider log. User-facing events still reach ainb-notifyd over its Unix socket. The same notify.sh powers ATC structured control when installed with AINBMANAGED=atc. stallguard.py additionally blocks turn-end when a session would idle on i.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.