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-article-draftgit 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-article-draft)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/content-article-draft"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/content-article-draft.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.00081 | $0.01141 |
| Opus 5 | $0.00041 | $0.00571 |
| Sonnet 5 | $0.00016 | $0.00228 |
| Haiku 4.5 | $0.00008 | $0.00114 |
Grade A, and why
content-article-draft 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 6d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
content-article-draft — Article draft
Goal: turn material into a first working draft of a 3-10k character article. Not a final version — the user polishes that themselves. The draft needs the right skeleton and tone.
Before starting, read:
~/.claude/rules/content-voice.md~/.claude/rules/content-formatting.md— the articles section
Step 1. Context
Ask:
- the topic in one sentence
- the audience: technical specialists at a certain level? Managers? Beginners?
- the platform: Habr / Medium / dev.to / personal blog / Telegraph?
- the source material: notes, experience, a project, an existing draft?
- the article's goal: teach something / share experience / break down a case / a provocative essay?
Step 2. Formulate the thesis
An article's thesis is a single claim that the author defends or illustrates. Not a topic, but a claim.
| Topic (bad) | Thesis (good) |
|---|---|
| "Microservices" | "Microservices are only worth the complexity when you genuinely have different release cycles or languages" |
| "Postgres vs Mongo" | "For most startups, Postgres covers 95% of the needs, and the remaining 5% don't justify a second database" |
| "My experience with k8s" | "After a year running k8s in production, I realized the main risk isn't complexity, but the blurring of SRE vs. dev responsibility" |
Show the thesis to the user and ask them to confirm or correct it. The thesis is the foundation.
Step 3. Build the skeleton
Standard structure:
# <Title>
> **TL;DR:** <thesis in 1-2 phrases + a brief summary>
## <Subheading 1: context / problem>
<Why this is interesting. A concrete real-life example.>
## <Subheading 2: argument / breakdown / solution>
<The main point. Code, diagrams, numbers.>
## <Subheading 3: nuances / counterarguments>
<Where the thesis doesn't hold. Where there are caveats.>
## <Subheading 4: application / summary>
<What the reader can do with all of this.>
---
<signature / author / links to resources>
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.
- 6d ago First seen · 132 lines · 81 tokens per session scan A 1a694d96ddde
content-article-draft is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 18d ago), licensed MIT. It adds 81 tokens to every session and 1,141 once invoked, about $0.0004 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
loop-engineering
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
obsidian
Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.4.1, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use…
agent-teams-command
Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
agentic-engineering
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
graph-engineering
Use when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.
harness-engineering
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.