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-testgit 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-test)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/id-test"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/id-test.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.1 | $0.00293 | $0.03658 |
| Opus 5 | $0.00147 | $0.01829 |
| Sonnet 5 | $0.00059 | $0.00732 |
| Haiku 4.5 | $0.00029 | $0.00366 |
Grade A, and why
id-test 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 3d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
id-test — read-only infra policy/contract TEST craft (infra-delivery step 7)
The infra-delivery step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an infra change → merge. Step 7 is the TEST step: after
id-validate (step 6, the static fmt/lint/render pass) and before id-plan (step 8, the read-only
pre-merge plan/diff seam), id-test runs the infra test suite against the change. That test
suite is the active profile's EXISTING read-only infra_binding.policy slot — the
policy-as-code / contract tests (conftest test / OPA over kustomize build / helm template
output) — backstopped by tofu validate (structural sanity). It then records the
pass/fail observation as a .foundry/-partitioned STEP-REPORT NOTE (.foundry/id-test-report),
an advisory artifact the operator + downstream steps read.
It is a PROCEDURE skill the generic agent runs: the conftest test +
tofu validate reads are both read-only. It is read-only — nothing in the live env is mutated.
ADVISORY — not a gate, records a step-report NOTE (not walk-evidence)
This skill is ADVISORY. It records the pass/fail observation and surfaces the verdict for
the operator; it does NOT gate, approve, or block any merge, and it does NOT self-certify a
PASS (the skill supplies the STEPS; the merge floor — the adopter's branch protection + CI checks,
see docs/merge-floor.md — is the merge authority). It never claims a machine-adjudicated
GREEN verdict.
Evidence — a .foundry/ step-report note, not a dedicated plan recorder. A standalone
policy-test pass/fail runs no tofu plan, so it has no plan_results / plan-evidence
surface. id-test records a .foundry/-partitioned STEP-REPORT NOTE (.foundry/id-test-report)
— a free-form advisory artifact that is NOT walk-evidence and NOT a verdict input. Honest
disclosure: the bespoke emit_infra_walk_evidence plan recorder this note used to be contrasted
against as "the id-plan step's producer" does not exist in scripts/ — retired. (The post-deploy realization producer emit_realization_evidence is real and is also not
id-test's — it is owned by id-sync / id-verify / id-rollback.)
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.
- 3d ago First seen · 174 lines · 293 tokens per session scan A 4ff79f1f0b28
id-test is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 2d ago), licensed MIT. It adds 293 tokens to every session and 3,658 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-09-03.
Other skills, from other repositories
journey-simulation
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…
are-you-done
A completion checker for coding work that asks for evidence before allowing an assistant to say a task is finished.
yolo-verify
Use to check a feature's work against its successcriteria and record the result. Produces verification.md and, on pass, the YOLO-Verified trailer. Triggers on "verify this", "does it meet the criteria", or as the verify step of yolo-feature.
test-architect
Acts as a Principal Test Architect to plan, write, prune, run, and hand off automated tests for any codebase in any language or framework — never touching production code, never committing, never running against production. Use whenever the user wants to add, fix, expand, refactor, or review tests for a feature, bug…
scenarios-from-requirements
Write brutally thorough, fully-traceable test scenarios from a requirement — a Jira/Confluence (or Trello/Linear/Azure DevOps/GitHub Issues) source of truth — BEFORE any test code, then a self-contained HTML/CSV coverage report. This is the requirements-first counterpart to the Test Architect: it trusts the spec and…
g-review
Run the review gate on the current branch diff. Runs the test suite, captures the diff, and dispatches code-lead, which verifies done conditions and reviews the diff itself. Issues MERGE READY or HOLD.