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 skills add lukasrepublic/agentic-foundry --skill reposgit clone --depth 1 https://github.com/lukasrepublic/agentic-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/skills/lukasrepublic/agentic-foundry/repos)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/repos"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/repos/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/skills/lukasrepublic/agentic-foundry/repos"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/repos.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.00107 | $0.01346 |
| Opus 5 | $0.00053 | $0.00673 |
| Sonnet 5 | $0.00021 | $0.00269 |
| Haiku 4.5 | $0.00011 | $0.00135 |
Grade A, and why
repos 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/foundry:repos
The control plane's fleet verbs over .claude/foundry-project.json's repos{} — the
repo/vcstool/meta/myrepos category's universal triad (sync / status / foreach), plus the
round-trip validator (validate). scripts/foundry_repo_fleet.py consumes
scripts/foundry_repo_registry.py's read-only classification — it does not re-derive it — and
adds the one thing the registry atom deliberately left out: verbs that act.
Not to be confused with /foundry:fleet. /foundry:fleet is the session roster — one row
per active Claude Code session, governing no repository at all. /foundry:repos governs the
repos{} manifest's hosted repositories. The two are fleet-shaped and share nothing else.
The four verbs
| verb | what it does |
|---|---|
sync |
idempotent reconcile: clone every not-cloned row that declares a remote, fetch every present row whose origin is exactly match, report everything else untouched |
status |
one honest line per repos.<key> entry: present · origin · branch · ahead/behind · dirty |
foreach -- <cmd…> |
shell-free argv fan-out of <cmd…> over the present repos, fail-collecting — one failing repo never stops the rest |
validate |
the manifest ⟷ reality ⟷ gitignore round trip, including the reverse direction: a git checkout on disk with no repos{} row is reported undeclared-checkout |
scripts/foundry_repo_fleet.py sync --root . [--json] [--timeout SECONDS]
scripts/foundry_repo_fleet.py status --root . [--json]
scripts/foundry_repo_fleet.py foreach --root . [--json] [--timeout SECONDS] -- git status --short
scripts/foundry_repo_fleet.py validate --root . [--json] [--max-depth N]
Clone and fetch are the entire mutation vocabulary
No checkout, reset, merge, rebase, pull, push, clean, stash, branch, remote or submodule command —
and no --force/-f/--hard/--force-sync — exists anywhere in this tool's vocabulary. An
existing checkout is never rewritten: a dirty, diverged, or origin-mismatched row is reported,
never touched. fetch moves remote-tracking refs and nothing else; advancing a working tree is the
operator's move (or the child repo's own loop), never this control plane's.
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.
- 6d ago First seen · 74 lines · 107 tokens per session scan A fee0b27fec84
repos is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 5d ago), licensed MIT. It adds 107 tokens to every session and 1,346 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
cleanup
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.
merge
Merge the reviewed pull request for the current branch, then hand straight off to cleanup. A sentence of editorial direction alongside the green light is read as a rider. Use when a human green-lights an open PR.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.