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 skills/lukasrepublic/agentic-foundry/id-applynpx skills add lukasrepublic/agentic-foundry --skill id-applygit 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/id-apply)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/id-apply"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/id-apply.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.00291 | $0.02800 |
| Opus 5 | $0.00146 | $0.01400 |
| Sonnet 5 | $0.00058 | $0.00560 |
| Haiku 4.5 | $0.00029 | $0.00280 |
Grade A, and why
id-apply 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 4d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/foundry:id-apply — the apply router (EXECUTE | VERIFY_ONLY | REFUSE)
The infra-delivery step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an IaC change spec → merge → realize. Step 12 is the
apply router: the one place the framework may MUTATE infrastructure. Infrastructure has no
app to boot; the merge floor already authorized the merge. id-apply is the disciplined procedure
the generic agent runs after merge to realize the change — resolving the profile, letting the
gate re-derive the change's GitOps classification from the frozen scope, and driving the closed
outcome that falls out, fail-closed.
The operator supplies the AWS context. The operator has already configured a correctly-scoped AWS
context (credentials + connectivity); its IAM restrictions ARE the control on what the mutating
command may do, and that control is outside the framework's scope — the framework relies on it and
does not model, verify, re-derive or second-guess it. The framework never acquires credentials or
connectivity: it runs no aws sso login, no aws configure, no assume-role, and establishes no VPN —
those are the operator's job, done before this skill ever runs. The framework never mutates in the
VERIFY_ONLY / REFUSE branches.
When to trigger
- The
infra-deliverysequence advances to the apply router (step 12), after an IaC change is merged and must be realized into the environment. - The operator says "
/foundry:id-apply", "run the apply router", or "apply this merged infra change".
ADVISORY — this skill advises the trusted operator; it is NOT the merge authority
This skill is an ADVISORY craft procedure + mechanical mistake-catcher FOR the trusted
operator. It realizes a merged change; it is NOT a merge gate and does NOT self-certify a
merge. The merge floor (the adopter's branch protection + CI checks — see the plugin's
docs/merge-floor.md) already authorized the merge; id-apply is the post-merge REALIZE gate,
not a second merge authority. The decision authority is decide_apply (a pure, total, fail-closed
function that derives the class itself) — this procedure drives the I/O around it.
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.
- 4d ago First seen · 140 lines · 291 tokens per session scan A 3fda02257b1a
id-apply is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 3d ago), licensed MIT. It adds 291 tokens to every session and 2,800 once invoked, about $0.0015 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-31.
Other skills, from other repositories
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.
outsystems-mcp
You are connected to OutSystems over the MCP HTTP transport. OutSystems is a cloud-native low-code platform where apps are built from OML (OutSystems Model Language), a binary format describing entities, screens, actions, and logic. Every tool call carries the harness's validated OAuth bearer; tenant + user identity…
writing-javascript
How browser JavaScript is written in this repo — both surfaces now speak one modern dialect and this says what that means for the code you type, where ES modules are impossible and where they are merely unused, and how to pick a feature (Baseline plus a file:// gate). Covers functional idiom over imperative DOM work…
writing-python
How Python is written in this repo — free functions over classes, structured returns instead of mutated arguments, comprehensions, no module state, and the stdlib-only, annotation-free, Python 3.8 dialect the AST lints enforce. Covers modular structure and the import-layer rule, DRY without copying a helper into a…
dora-expert
DORA expert for EU financial entities. Deep knowledge of Digital Operational Resilience Act including 5 pillars, ICT risk management, incident reporting, resilience testing, third-party oversight, and information sharing for financial sector digital resilience.