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 dhaupin/vant --skill vant-skill-audit-cigit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-audit-ci)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-audit-ci"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-audit-ci/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/dhaupin/vant/vant-skill-audit-ci"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-audit-ci.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.00007 | $0.00438 |
| Opus 5.5 | $0.00003 | $0.00175 |
| Sonnet 5.5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
audit-ci 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 4d 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.
What it actually says
CI Audit
Does CI work?
What To Check
1. Pipeline Exists
# Common CI files
ls .github/workflows/
ls .gitlab-ci.yml
ls Jenkinsfile
ls .circleci/config.yml
| File | CI |
|---|---|
| .github/workflows/*.yml | GitHub |
| .gitlab-ci.yml | GitLab |
| Jenkinsfile | Jenkins |
| .circleci/config.yml | Circle |
2. Pipeline Runs
# Check recent runs
gh run list
| Status | Meaning |
|---|---|
| ✓ success | Working |
| ✗ failure | Broken |
| ○ pending | Running |
3. Pipeline Steps
jobs:
build:
steps:
- run: npm test
- run: npm build
| Check | Issue |
|---|---|
| Tests run | No tests |
| Build runs | No build |
| Deploy runs | No deploy |
4. Caching
- uses: actions/cache@v3
with:
path: node_modules
| Check | Issue | Fix |
|---|---|---|
| No cache | Slow builds | Add cache |
| Cache all | Inefficient | Cache key |
Output
## CI Audit
### Pipeline
- [PRESENT/MISSING] File: [file]
- [PASS/FAIL] Last run: [status]
### Steps
- [YES/NO] Test
- [YES/NO] Build
- [YES/NO] Deploy
### Timing
- Test: [s]s
- Build: [s]s
- Total: [s]s
### Issues
- [list]
Role: CI Auditor Input: Repository Output: CI works?
Keep CI green.
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.
- 4d ago Changed · -2 lines 243d8efb19bd
- 2mo ago First seen · 109 lines · 7 tokens per session scan A 25cb586ffde6
audit-ci is a skill published in the GitHub repository dhaupin/vant (15 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 438 once invoked, about $0.0000 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
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
fast-agent-design
Use this skill to generate well-branded interfaces and assets for fast-agent, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for protoyping.
ci-troubleshoot
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to know which workflow does…
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.
knowledge-engineering-quality-and-delivery-build-release-and-documentation
A delivery system for building, testing, versioning, publishing, and documenting a TypeScript monorepo, which is one repository containing multiple related packages.