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/JairoTorregrosa/jaiskillsWrote 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/commands/jairotorregrosa/jaiskills/constatar-run)<a href="https://agentmods.dev/commands/jairotorregrosa/jaiskills/constatar-run"><img src="https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/constatar-run/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/commands/jairotorregrosa/jaiskills/constatar-run"><img src="https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/constatar-run.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.00011 | $0.00262 |
| Opus 5 | $0.00005 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
constatar-run 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 9d 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
Execute a constatar plan end to end.
- Load the constatar-verify and constatar-plan skills' rules (verification ladder, invariants).
constatar preflight— abort with the error if adapters are missing.- Parse arguments:
$ARGUMENTS= plan file, optional run dir (defaultruns/<plan-name>-<date>). - If the plan's repo has uncommitted changes, stop and tell the user (the engine will refuse with DirtyRepo; do not stash or commit for them without asking).
constatar run <plan> --run-dir <run-dir>— stream progress to the user.- On success:
constatar inspect --conformance --run-dir <run-dir> --plan <plan> --assert-all-pass, then summarize per unit: verification rungs passed, evidence highlights, cost (inspect --cost). - On failure: report the failing unit, rung, and error verbatim; list surviving
constatar/<unit>branches; suggestconstatar resumeafter the cause is fixed. Never re-run units by hand.
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.
- 9d ago First seen · 15 lines · 11 tokens per session scan A 2fd1cff404c2
constatar-run is a command published in the GitHub repository JairoTorregrosa/jaiskills (5 stars, last pushed 9d ago), licensed MIT. It adds 11 tokens to every session and 262 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
test-browser
Run browser tests on pages affected by current PR or branch.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
pn-audit-design-tokens
Surgical design-token audit — CSS custom property coverage, token naming, dark-mode correctness, and hardcoded value elimination. Standalone or chained by pn-frontend-audit.
add-specs
Add specs using a structured testing approach.
add-tests
Add tests using a structured testing approach.