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 id-rollbackgit 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-rollback)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/id-rollback"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/id-rollback/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/id-rollback"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/id-rollback.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.00398 | $0.04013 |
| Opus 5.5 | $0.00159 | $0.01605 |
| Sonnet 5.5 | $0.00080 | $0.00803 |
| Haiku 4.5 | $0.00040 | $0.00401 |
Grade A, and why
id-rollback 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
id-rollback — the incident safe-revert procedure (git revert → reconcile → verify-landed)
The infra-delivery step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships)'s incident path. When a delivered change did NOT land — a
NOT-LANDED realization (the derive_realization_verdict consequence), an escaped defect, bad
config — the operator runs this safe-revert PROCEDURE to restore the last-known-good IaC and
prove reality matches it again. The shape is git revert → reconcile → verify-landed:
revert the offending commit (restoring the prior authorized IaC via the governed
/foundry:revert), drive the GitOps controller's idempotent reconcile toward the reverted
IaC, then run the realization read through the post-deploy realization frame — ArgoCD
Synced ∧ Healthy + post-revert tofu plan == ∅ against the reverted IaC ⇒ the revert
LANDED (the incident is closed); a residual OutOfSync / non-empty plan ⇒ NOT-LANDED
(the revert itself did not realize — escalate). It is a PROCEDURE skill the generic agent runs.
ADVISORY — observe-and-record, the floor re-derives, the skill self-certifies nothing
This skill is ADVISORY. The post-deploy realization frame is an observe-and-record path
(the id-sync/id-verify discipline): id-rollback records the post-revert realization
observation; the realization gate (derive_realization_verdict — a real, live function) +
deploy-status adjudicate the recorded signals — the skill self-certifies NOTHING. The revert
restores a previously authorized state through the governed /foundry:revert: it reuses the
prior authorization (no new contract), is still subject to the merge floor, and is NOT a
skip of the no-skip front-authorization gate — the revert's reused authorization + the realization
observation are surfaced to the operator/reviewer at the merge floor (the adopter's branch
protection + CI checks — see docs/merge-floor.md). The both-modes floor is
unchanged: front-authorization, the merge floor, security review,
typed contracts. Craft guidance FOR the trusted operator, not a defense against them.
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 · 191 lines · 398 tokens per session scan A 6867dce16155
id-rollback is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 3d ago), licensed MIT. It adds 398 tokens to every session and 4,013 once invoked, about $0.0016 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-08-31.
Other skills, from other repositories
gh-monitor-pr
Start a detached GitHub pull-request monitor that wakes the exact launching Codex Desktop or CLI root through the managed Codex App Server when review, CI, conflict, merge-queue, closure, readiness, or merge events need attention. Use when the user asks Codex to watch, monitor, babysit, or wait on a PR or merge queue…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
pre-release-review
Run the pre-release gate for this multi-plugin monorepo: establish each plugin's release boundary from its last reachable tag to HEAD, audit every changed plugin's [Unreleased] changelog against the actual code diff, identify contract-surface and breaking changes, and, per the objective the user picks up front, either…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
fleet-release
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release…
fleet-release
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release…