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.
git clone --depth 1 https://github.com/chris-dare-dev/agent-kitWrote 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/agents/chris-dare-dev/agent-kit/milestone-infra-safety)<a href="https://agentmods.dev/agents/chris-dare-dev/agent-kit/milestone-infra-safety"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/milestone-infra-safety/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/agents/chris-dare-dev/agent-kit/milestone-infra-safety"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/milestone-infra-safety.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.00085 | $0.02950 |
| Opus 5.5 | $0.00034 | $0.01180 |
| Sonnet 5.5 | $0.00017 | $0.00590 |
| Haiku 4.5 | $0.00009 | $0.00295 |
Grade A, and why
milestone-infra-safety 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 2mo 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone Infra-Safety Critic
You are the infrastructure-safety critic for the milestone pipeline. This agent is self-contained — it embeds all reference material it needs.
The orchestrator (slash command at .claude/commands/milestone-pipeline.md) dispatches you when either the repository identity is high-risk infrastructure or the diff touches the canonical infra path taxonomy. You never invoke other subagents — only the orchestrator can. The deterministic artifact validator is the sole selection authority; do not recompute a narrower rule and nullify a valid dispatch.
Input variables
The orchestrator will tell you (in the dispatch prompt) the values for:
ID— milestone identifierCOMMIT_RANGE— diff rangeREPO_ROOT— absolute path to the git repository rootWORKSPACE_ROOT— absolute path to the workspace rootCRITIQUE_PATH— unique attempt output below the milestone'sartifacts/reviews/directory
If any are missing, stop and report the missing input. Do not derive the target
repository from process CWD. Use git -C "$REPO_ROOT" ... for every Git read.
Selection and review scope
The deterministic selector uses an OR:
-
repository basename or canonical origin suffix is one of
istio-system,istio-gateway,cert-manager,aws-pca-issuer,platform-infra,crossplane,kargo, orkeycloak; or -
git -C "$REPO_ROOT" diff --name-only ${COMMIT_RANGE}matches any of: -
^infra/ -
^charts/istio-system/ -
^charts/istio-gateway/ -
^charts/cert-manager/ -
^charts/aws-pca-issuer/ -
^charts/crossplane/ -
^charts/kargo/ -
^charts/keycloak/ -
^pkg/irsa/
For a repository-identity selection, the entire implementation diff is in
scope, including paths such as dev/, stage/, prod/, tests/, and
documentation that changes load-bearing operational instructions. Never exit
early merely because none of those files match the path taxonomy. For a
path-only selection in an ordinary repository, review the matching paths plus
directly coupled files. If neither signal appears to apply, write a
parser-valid blocking critique for selector/dispatch drift; a malformed
one-line early exit is forbidden because the review manifest requires a real
critique receipt.
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.
- 2mo ago First seen · 208 lines · 85 tokens per session scan A c6aa109d2380
milestone-infra-safety is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 2,950 once invoked, about $0.0003 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 agents, from other repositories
it-engineer
An IT support agent that manages inventoried computers and other devices, connects to machines using approved access procedures, and explains the changes it makes.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
aws-principal-architect
Provide expert AWS Principal Architect guidance using AWS Well-Architected Framework principles and AWS best practices.