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/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/validate-qmd)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/validate-qmd"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/validate-qmd.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.00013 | $0.00983 |
| Opus 5 | $0.00006 | $0.00491 |
| Sonnet 5 | $0.00003 | $0.00197 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
validate-qmd 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QMD Validation Command
Validate files against Queryable Markdown (QMD) standard for token-efficient retrieval.
Usage
/docs:validate-qmd <path> [options]
Arguments
| Argument | Required | Description |
|---|---|---|
<path> |
Yes | File, folder, or glob pattern |
--fix |
No | Show fix suggestions |
--verbose |
No | Show all checks (not just failures) |
Validation Rules
Frontmatter (Required)
| Rule | Check | Fix |
|---|---|---|
| FM-01 | Has frontmatter (--- delimiters) |
Add YAML frontmatter |
| FM-02 | Has name: field |
Add identifier |
| FM-03 | Has description: (< 100 chars) |
Shorten description |
| FM-04 | Has layer: (1-4) |
Add layer number |
| FM-05 | Has keywords: array |
Add grep targets |
| FM-06 | Frontmatter ≤ 20 lines | Reduce frontmatter |
Structure (Required)
| Rule | Check | Fix |
|---|---|---|
| ST-01 | Has ## Summary heading |
Add summary section |
| ST-02 | Summary ≤ 10 lines | Shorten summary |
| ST-03 | Has ## Quick Reference heading |
Add quick ref section |
| ST-04 | Major sections separated by --- |
Add horizontal rules |
Heading Hierarchy (Recommended)
| Rule | Check | Fix |
|---|---|---|
| HH-01 | Single # Title at top |
Fix heading levels |
| HH-02 | ## for major sections |
Use level-2 headings |
| HH-03 | ### for subsections |
Use level-3 for subs |
| HH-04 | No skipped levels | Fix # → ### gaps |
Grep-Friendliness (Index Files)
| Rule | Check | Fix |
|---|---|---|
| GF-01 | Tables use | col | format |
Reformat to tables |
| GF-02 | One entry per line | Split multi-line entries |
Section Detection
QMD uses markdown-native section detection:
## Section A ← Section starts at ## heading
Content...
--- ← Section ends at --- or next ##
## Section B ← Next section starts
Validation checks:
- Required headings exist:
## Summary,## Quick Reference - Sections are separated by
---horizontal rules - No orphaned content before first
##
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 · 143 lines · 13 tokens per session scan A 613f0c19ee8f
validate-qmd is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 983 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-30.
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.