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 alexeyshishin/as-skill --skill content-documentationgit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/content-documentation)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/content-documentation"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/content-documentation.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.00090 | $0.01192 |
| Opus 5 | $0.00045 | $0.00596 |
| Sonnet 5 | $0.00018 | $0.00238 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
content-documentation 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
content-documentation — Technical documentation skeleton
Goal: give the reader a reproducible path from their starting state to the goal. Not theory, not an essay — a step-by-step set of instructions where every step is verifiable.
Before starting, read:
~/.claude/rules/content-voice.md~/.claude/rules/content-formatting.md— the tutorials section
Step 1. Define the scope
Ask:
- the tutorial's goal: "after reading this, the reader will be able to <verb + result>"
- examples: "deploy a Postgres cluster with replication across 3 nodes," "set up OAuth login via Google in an Express app," "measure heap allocations in a Go service"
- the reader's starting state: what they have, what's assumed
- the final state: what should be working at the end
- the platform / stack: versions, OS, cloud
If the goal is vague ("a tutorial on k8s") — stop and help narrow it down to specifics. A tutorial "on k8s" is impossible — "deploy minikube + deploy a stateless API + expose via Ingress" is possible.
Step 2. Build the skeleton
# <Title: verb + result>
> **Goal:** after completing this tutorial you'll be able to _<specifically>_.
> **Time:** ~X minutes.
> **Level:** beginner / intermediate / advanced.
## What you'll need
- <tooling: version>
- <tooling: version>
- <access: where to get it>
- <cloud/environment, if applicable>
## Step 1. <Verb + what>
<1-2 lines of context: what we're doing and why.>
```<lang>
<command>
Check: <expected result / a command confirming success>
Step 2. <Verb + what>
...
Step N. <Verb + what>
...
Verifying the final state
Troubleshooting
<Symptom 1>
Cause: ... Fix: ...
<Symptom 2>
...
Cleanup
<commands to roll back everything that was created — if the reader doesn't want to keep it>
What's next
<2-3 links: deeper dives, related tutorials, docs>
## Step 3. Agree on the skeleton
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 148 lines · 90 tokens per session scan A 53151f6f60a2
content-documentation is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 19d ago), licensed MIT. It adds 90 tokens to every session and 1,192 once invoked, about $0.0005 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-31.
Other skills, from other repositories
cognitive-compile
Use when source material must be transformed into a compact, evidence-aware model for learning, decisions, or an Obsidian concept note.
guide
Interactive 8-module learning path for the shipped skills, role-adaptive.
pdf-courseware-to-obsidian
A workflow that turns local PDF or PowerPoint course materials into structured Chinese study notes in an Obsidian vault. Obsidian is a note-taking app that stores linked Markdown files and related images.
lc-logger
Log a LeetCode problem into the user's Obsidian interview-prep tracker (daily notes + Dataview dashboard). Trigger whenever the user pastes a leetcode.com problem URL — even with no other words — or says anything like "log this", "log this lc problem", "just did/solved a problem", "add two sum to my log", "did 239…
yt-digest
Turn a YouTube URL into a vault-ready research digest — transcript, key learning moments with timestamp deep-links, and screenshots of visual moments (slides, demos, dashboards). Use when the user pastes a YouTube link they're researching, says "summarize this video", "/yt-digest ", "youtube digest", or asks to…
context7-mcp
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.