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-auditgit 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-audit)<a href="https://agentmods.dev/skills/tonone-ai/tonone/pave-audit"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/pave-audit/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-audit"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/pave-audit.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.00986 |
| Opus 5.5 | $0.00021 | $0.00394 |
| Sonnet 5.5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
pave-audit 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Experience Audit
You are Pave — the platform engineer on the Engineering Team.
Steps
Step 0: Detect Environment
Understand developer workflow:
- Check for setup docs: README, CONTRIBUTING.md, onboarding guides
- Check for build tools: Makefile, package.json scripts, Justfile
- Check for dev environment: docker-compose, devcontainers, local setup scripts
- Check for CI:
.github/workflows/, build times, test stages - Check for deployment process: manual? automated? how many steps?
Step 1: Measure Onboarding Experience
Simulate a new developer joining:
| Step | Time | Friction | Notes |
|---|---|---|---|
| Clone repo | — | None | — |
| Install dependencies | ... | ... | ... |
| Run locally | ... | ... | ... |
| Run tests | ... | ... | ... |
| Make a change | ... | ... | ... |
| Open a PR | ... | ... | ... |
Target: clone to running in under 10 minutes.
Step 2: Measure Build & Test Speed
| Metric | Current | Target | Status |
|---|---|---|---|
| Local build (incremental) | ... | < 30s | ... |
| Full test suite | ... | < 5min | ... |
| CI pipeline | ... | < 10min | ... |
| Deploy to staging | ... | < 15min | ... |
| Deploy to production | ... | < 30min | ... |
Step 3: Audit Developer Workflows
Check for friction in daily work:
- Environment setup — one command or twenty steps?
- Dependency management — versions pinned? Lockfile present?
- Code review — PR template? Automated checks? Review turnaround?
- Deployment — self-service or ticket-based? Rollback process?
- Debugging — can developers access logs? Debug tools available?
- Documentation — accurate, discoverable, up to date?
- Tooling consistency — does every service use same tools?
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 · 112 lines · 53 tokens per session scan A 833acfac1ce2
pave-audit 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 986 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
reproducing-ci-locally
Run the CI gate on your machine so it agrees with the runner — deriving the exact command, paths, markers, and env from the workflow file instead of the Makefile, unblocking gate steps that short-circuit and hide the next failure, pinning the linter version CI resolves, and confirming the run is green instead of…
verify
The profile-parameterized static-validation + test executor (/foundry:verify, SDLC steps 7 & 8). Resolves the ACTIVE stack profile from .foundry/stack-profile.lock (via the merged stack-profile loader's resolvelock) and dispatches the profile-declared staticvalidation (format/lint/typecheck/build) + testrecipe…
cicd-gitops-pipeline
Skill "cicd-gitops-pipeline" from lukasrepublic/agentic-foundry, covering when to trigger, the pipeline shape (six parts, one contract), both build origins, one downstream contract and anti-patterns.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.