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 skills/tykisgod/quick-question/doc-tidynpx skills add tykisgod/quick-question --skill doc-tidygit clone --depth 1 https://github.com/tykisgod/quick-questionWrote 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/skills/tykisgod/quick-question/doc-tidy)<a href="https://agentmods.dev/skills/tykisgod/quick-question/doc-tidy"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/doc-tidy.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 | $0.00024 | $0.00779 |
| Opus 5 | $0.00012 | $0.00390 |
| Sonnet 5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
doc-tidy 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 4d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Scan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made.
Execution Steps
1. Full Scan
Dispatch 3 parallel Explore subagents (model: haiku) to collect a documentation inventory:
Subagent A — Root + Docs/
- All .md files in root directory (except CLAUDE.md, AGENTS.md)
- All files and directory structure under Docs/ (recursive)
- For each file: path, first line content, line count
Subagent B — In-code documentation under Assets/
- All .md files under Assets/ (recursive)
- Including README, ARCHITECTURE, API_REFERENCE, CHANGELOG, AGENTS.md, etc.
- For each file: path, first line content, line count
Subagent C — Config & tool documentation
- .claude/ directory structure
- Documentation under scripts/
- Templates under .github/
- Root config files (.mcp.json, opencode.json, etc.)
2. Classify
Categorize all documents by:
| Category | Description |
|---|---|
| Long-term design | System architecture, module design, data config (should be centrally managed) |
| In-code docs | README, API reference, dev guides (should live with the code) |
| Branch artifacts | Review outputs, spec files, timelines (should be archived after merge) |
| Temporary files | tmp-*, one-off bug reports, old prompts (should be cleaned or archived) |
| Project entry points | CLAUDE.md, AGENTS.md, PR templates (should stay in root) |
| Tool config | Skills, hooks, script docs (each has its place, don't move) |
3. Find Issues
Check and report:
- Root pollution: files in root that shouldn't be there
- Unorganized accumulation: directories with >10 files and no subdirectory structure
- Temporal mixing: long-term docs and temporary artifacts in the same directory
- Duplicate docs: files with highly similar names or content across directories
- Orphaned docs: documents referencing deleted modules or outdated code
- Missing docs: Service modules with code but no documentation at all
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.
- 4d ago First seen · 89 lines · 24 tokens per session scan A 00984c698a84
doc-tidy is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 10d ago), licensed MIT. It adds 24 tokens to every session and 779 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 skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…