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 agentmods add skills/sentasity/cadence/c-validatenpx skills add sentasity/cadence --skill c-validategit clone --depth 1 https://github.com/sentasity/cadenceWrote 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/sentasity/cadence/c-validate)<a href="https://agentmods.dev/skills/sentasity/cadence/c-validate"><img src="https://agentmods.dev/badge/skills/sentasity/cadence/c-validate.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 | $0.00076 | $0.01519 |
| Opus 5 | $0.00038 | $0.00759 |
| Sonnet 5 | $0.00015 | $0.00304 |
| Haiku 4.5 | $0.00008 | $0.00152 |
Grade A, and why
c-validate scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**2. Category A — Automated.** Run each item itself: `curl`, `psql`, `pytest`, etc. Mark `- [x]` as each passes. Stop on first failure; surface exact output for user resolution. How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/c-validate
You walk a plan's post-deploy validation doc. You do NOT deploy. You verify deployed behavior by running automated checks, asking the user to do manual UI work, and checking observable signals.
Invocation
/c-validate <path-to-plan-folder>
Status gates
| Plan status | Behavior |
|---|---|
draft / in-progress |
Refuse: "Plan isn't implemented yet. Run /c-execute first." |
implemented |
Run the walk. |
completed |
Run anyway (re-validation after a re-deploy). Reset checkboxes per config. |
on-hold / superseded |
Refuse with status-mismatch error. |
Walk order (strict)
Recommendation note (once, at the start of the walk). Per skills/_shared/browser-validation.md: if this plan's 96-validation.md has at least one Category B item with an e2e: reference AND no runner is configured or detected (validate.browser_command left at default npx playwright test and auto detection finds no suite), print one informational line recommending a runner (Playwright by default), then proceed — those items take the manual fallback. A repo with a runner configured/detected prints nothing. Once per run; never nag.
1. Category C — Prerequisites first. Read the plan's 96-validation once via skills/_shared/storage-resolution.md (read_artifact); for section C print the prereq list, ask user to confirm each: "Backend deployed? Migration run? Test users seeded? (y/each)" Walk BLOCKS until every C item confirmed. No prereq = no validation.
2. Category A — Automated. Run each item itself: curl, psql, pytest, etc. Mark - [x] as each passes. Stop on first failure; surface exact output for user resolution.
3. Category B — Manual workflow last. Resolve validate.browser_driver to delegate-or-manual once at the start of this pass, per skills/_shared/browser-validation.md (auto runs suite detection and delegates if found; playwright forces delegation; manual forces manual). Then, for each Category B item:
- If the driver resolved to delegate AND the item carries an
e2e:line → delegate. Compose<browser_env_preamble> && <browser_command> <spec> -g "<grep>"(drop the&&prefix if no preamble; drop-gif the item has none), run it headless and non-interactively, and map the exit code: exit 0 → mark- [x]; non-zero → a validation failure, routed through the existing Failure handling section below (stop the walk, surface exact output, offer Fix / OOS / Abort). No new failure path. - Otherwise → manual (today's behavior). Print the human-readable step list ("Log in as X → click Y → see Z"); user does the clicks; run the verification (DB query or API call) after each step or at walkthrough's end; mark
- [x]when verified.
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 First seen · 77 lines · 76 tokens per session scan A 006fdffa29df
c-validate is a skill published in the GitHub repository sentasity/cadence (1 stars, last pushed 9d ago), licensed MIT. It adds 76 tokens to every session and 1,519 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
roadmap-to-workflow
Fan an approved .task/roadmap/ .md out to a dynamic Workflow — parallel planning, serialized implementation, dependency-ordered waves.
to-plan
Capture the chat into .task/task/ .md with ## Description plus ## Plan (Goal/Touches/Logic) — the deepest one-task capture.
self-improve
Self-improve this skills repo — surface and (safely) apply quality improvements across four parallel read-only lenses (Clarity, Leanness, Coverage, Ergonomics). Sibling of /self-audit — audit fixes rule violations, improve raises quality where no rule is broken. Local meta-skill, independent of the /task: pipeline.
to-roadmap
Capture a multi-task initiative into .task/roadmap/ .md — a phase-grouped backlog of ready-to-pick-up items.
to-task
Capture the chat (or a roadmap item) into .task/task/ .md — ## Description only, no ## Plan.
self-audit
Self-audit this skills repo against CLAUDE.md invariants, the artifact contract, and README/CLAUDE.md/docs sync via three parallel read-only subagents. Local meta-skill — independent of the /task: pipeline.