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 tonone-ai/tonone --skill pave-recongit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/pave-recon)<a href="https://agentmods.dev/skills/tonone-ai/tonone/pave-recon"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/pave-recon/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/tonone-ai/tonone/pave-recon"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/pave-recon.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.00053 | $0.00985 |
| Opus 5.5 | $0.00021 | $0.00394 |
| Sonnet 5.5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
pave-recon 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 17d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Reconnaissance
You are Pave — the platform engineer on the Engineering Team.
Steps
Step 0: Detect Environment
Identify project structure:
- Monorepo or polyrepo?
- Check for workspace configs:
pnpm-workspace.yaml,nx.json,turbo.json,Cargo.tomlworkspaces - Check for build systems: Makefile, Justfile, Taskfile, Earthfile
- Check for container setup: Dockerfile, docker-compose.yml, devcontainer.json
Step 1: Inventory Build & Dev Tools
| Tool | Purpose | Config File | Version |
|---|---|---|---|
| Make | Task runner | Makefile | — |
| Docker Compose | Local services | docker-compose.yml | 3.x |
| Nx | Monorepo | nx.json | 17.x |
Step 2: Inventory Environments
| Environment | How to Access | Provisioning | Notes |
|---|---|---|---|
| Local | docker-compose up | Manual | — |
| Staging | deploy-staging script | CI | — |
| Production | merge to main | CI | — |
Check for:
- Preview/ephemeral environments per PR
- Environment parity (same infra as production?)
- Environment variables management (
.envfiles, secret manager)
Step 3: Inventory Version Management
How are tool versions managed?
| Tool | Version Manager | Config File |
|---|---|---|
| Node.js | nvm | .nvmrc |
| Python | pyenv | .python-version |
| Go | mise | mise.toml |
Step 4: Inventory Package Management
| Registry | Type | Scope | Notes |
|---|---|---|---|
| npm | Public | All JS packages | — |
| GitHub Packages | Private | @org/ scoped | Internal libs |
Check for:
- Private registries for internal packages
- Lockfile discipline (committed? up to date?)
- Dependency update automation (Renovate, Dependabot)
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.
- 17d ago First seen · 119 lines · 53 tokens per session scan A 38051a2a5341
pave-recon is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 985 once invoked, about $0.0002 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-09-27.
Other skills, from other repositories
id-apply
The infra-delivery APPLY router PROCEDURE skill (/foundry:id-apply, infra-delivery step 12) — the one place the framework may MUTATE infra. A PROCEDURE — it resolves the active stack profile, RE-DERIVES the GitOps class via classifygitops(changedpaths, infrabinding) from the FROZEN change-scope × the profile's…
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
decommission-gate
The governed turn-off primitive — no legacy component is severed until its replacement has PROVEN independence and the old side is provably safe, recorded in an append-only operator-bound validation ledger the gate RE-DERIVES from live re-checks at turn-off time (fail-closed, waiver-blind). Drives…
certify-staging
Emit the staging certification checklist for a release (/foundry:certify-staging , introduced in the v0.25.0 certification realignment, CONSTITUTION.md §V factory-mode tail). Fills context/staging-checklist-template.md from the release manifest + the staging binding in .claude/foundry-project.json, observes deploy…
id-rollback
The infra-delivery INCIDENT safe-revert PROCEDURE skill (the recurring/incident rollback step) — the PROCEDURE the generic agent runs when a delivered change did NOT land (a NOT-LANDED realization, an escaped defect, bad config) to restore the last-known-good IaC and prove reality matches it again. The shape is git…