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 skills add YoungjaeDev/my-claude-plugins --skill doc-guidesgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWrote 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/youngjaedev/my-claude-plugins/doc-guides)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/doc-guides"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/doc-guides.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.00070 | $0.01897 |
| Opus 5 | $0.00035 | $0.00949 |
| Sonnet 5 | $0.00014 | $0.00379 |
| Haiku 4.5 | $0.00007 | $0.00190 |
Grade A, and why
doc-guides 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 2d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Guides
Four writing-reference cards for the docs document commands, one per output type. Each
/docs:* command loads the matching section below deterministically: this skill is not
meant to be browsed top to bottom.
README
Patterns and best practices derived from awesome-readme examples.
Triggers
- "how to write readme"
- "readme best practices"
- "readme template"
- "improve my readme"
Quick Reference
Universal Structure
- Header (Logo + Badges + Tagline)
- Quick Start (3 steps max)
- Features (Benefits, not specs)
- Installation (Detailed)
- Usage/Examples (Progressive complexity)
- Configuration
- API/Props
- Contributing
- License
Essential Badges (Pick 3-5)
| Badge | Purpose |
|---|---|
| Build/CI | Trust - "it works" |
| Version | Currency |
| License | Legal clarity |
| Downloads | Social proof |
| Coverage | Quality signal |
CRO Essentials
- 5-second test: What, Who, Why visible?
- Quick start under 5 minutes
- Visual demo for UI projects
- "You should see:" verification
- Troubleshooting link nearby
References
For detailed patterns, see:
../../references/README_PATTERNS.md- Full pattern documentation../../references/TEMPLATES.md- Copy-paste templates../../references/CRO_CHECKLIST.md- Conversion optimization../../references/EXAMPLES_ANALYSIS.md- Analyzed examples
Templates Available
| Type | Use For |
|---|---|
| CLI Tool | Command-line applications |
| Library | npm/pip packages |
| React Component | UI components |
| MCP Plugin | Claude Code plugins |
| SaaS | Web applications |
| Desktop | Electron/native apps |
CHANGELOG
Writing patterns based on Keep a Changelog and Conventional Commits.
Triggers
- "how to write changelog"
- "changelog format"
- "changelog template"
- "keep a changelog"
Quick Reference
Standard Format
# Changelog
## [Unreleased]
### Added
- New feature
### Fixed
- Bug fix
## [1.0.0] - 2026-02-05
### Added
- Initial release
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.
- 2d ago First seen · 247 lines · 70 tokens per session scan A 846ed2cade37
doc-guides is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 1,897 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.