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 commands/thapaliyabikendra/ai-artifacts/optimize-mdgit 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/optimize-md)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/optimize-md"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/optimize-md.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.01039 |
| Opus 5 | $0.00006 | $0.00519 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
optimize-md 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 5d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Optimization Command
Analyze and optimize markdown files for maintainability, compaction, and structure.
Usage
/docs:optimize-md <path> [options]
Arguments
| Argument | Required | Description |
|---|---|---|
<path> |
Yes | File, folder, or glob pattern |
--profile <type> |
No | Force profile (auto-detected if omitted) |
--mode <mode> |
No | audit (default), apply, check |
--max-lines <N> |
No | Override line limit |
Modes
| Mode | Description |
|---|---|
audit |
Analyze and produce report (default) |
apply |
Implement changes (requires confirmation) |
check |
CI-friendly validation (exit 0/1) |
Profiles
Profiles are auto-detected from path. Apply markdown-optimization skill for full profile details.
Key limits (from GUIDELINES.md):
| Profile | Max Lines |
|---|---|
agent |
150 |
skill |
500 |
command |
200 |
guidelines |
1,000 |
generic |
Default |
See profiles.md for detection patterns and optimization rules.
Context
Apply the markdown-optimization skill before analysis for patterns and profile details.
Execution
1. Parse Arguments
Extract from $ARGUMENTS: path (required), profile, mode, max-lines.
2. Discover & Profile Files
Use Glob to find .md files. Auto-detect profile from path patterns.
3. Run Analysis
For each file, check:
- Size - Lines vs profile limit
- Structure - Heading hierarchy, TOC presence
- Duplication - Repeated content across files
- Links - Broken internal links
- Compaction - Prose → table opportunities
Guidelines profile adds: INDEX.md completeness, cross-references, folder structure, orphan detection. See profiles.md.
4. Execute Mode
Audit: Generate report, no modifications.
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.
- 5d ago First seen · 163 lines · 13 tokens per session scan A 4d8906d82252
optimize-md 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 1,039 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.