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/aivorynet/kronk-cmsWrote 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/aivorynet/kronk-cms/kronk-audit)<a href="https://agentmods.dev/commands/aivorynet/kronk-cms/kronk-audit"><img src="https://agentmods.dev/badge/commands/aivorynet/kronk-cms/kronk-audit.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.1 | $0.00000 | $0.00234 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
kronk-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 8d 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
Kronk Quality Audit
Run a quality audit on the content in this project.
Steps
- Detect Framework: Check
.kronk/config.yamlor auto-detect from config files - Find Content Files: Scan the content directory for markdown files
- Audit Each File for:
SEO
- Title exists and is under 60 characters
- Description exists and is 150-160 characters
- Proper heading hierarchy (h1 -> h2 -> h3)
- No duplicate titles
Accessibility
- All images have alt text
- Links have descriptive text (not "click here")
- Proper semantic structure
Performance
- No oversized image references
- Content is focused and well-structured
- No excessive inline styles
Security
- No hardcoded credentials or API keys
- External links use HTTPS
- No script injection vulnerabilities
Output
Provide a summary with:
- Total files checked
- Issues found by category (SEO, A11y, Perf, Security)
- Top 5 files with most issues
- Specific recommendations to fix
$ARGUMENTS
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.
- 8d ago First seen · 40 lines · 0 tokens per session scan A 2a790d1529a8
kronk-audit is a command published in the GitHub repository aivorynet/kronk-cms (11 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 234 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.