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-content)<a href="https://agentmods.dev/commands/aivorynet/kronk-cms/kronk-content"><img src="https://agentmods.dev/badge/commands/aivorynet/kronk-cms/kronk-content.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.00315 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
kronk-content 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 7d 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
Create Content with Kronk
You are creating content for a static site generator project managed by Kronk.
Project Context
First, get the project context by calling the Kronk MCP tool kronk/context if available, or read the .kronk/config.yaml file.
Framework Detection
Detect the framework using kronk/detect or check .kronk/config.yaml for the configured framework.
Content Guidelines
Based on the detected framework, follow these conventions:
Hugo:
- Use YAML or TOML front matter
- Place posts in
content/posts/ - Include: title, date, draft, tags, categories
- Use Hugo shortcodes where appropriate
Jekyll:
- Use YAML front matter
- Name posts as
YYYY-MM-DD-title.mdin_posts/ - Include: layout, title, date, categories, tags
Astro:
- Use YAML front matter in
.mdor.mdx - Place in
src/content/blog/ - Include: title, description, pubDate
Eleventy:
- Use YAML front matter
- Include: title, date, tags
Quality Guardrails
Apply these quality checks:
- SEO: Title under 60 chars, description 150-160 chars, proper heading hierarchy
- Accessibility: Descriptive alt text for images, semantic HTML
- Performance: Optimized image references, focused content
User Request
$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.
- 7d ago First seen · 42 lines · 0 tokens per session scan A ec7d33f0e64d
kronk-content is a command published in the GitHub repository aivorynet/kronk-cms (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 315 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.