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 causify-ai/helpers --skill blog.write_tutorial_readmegit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/blog.write_tutorial_readme)<a href="https://agentmods.dev/skills/causify-ai/helpers/blog.write_tutorial_readme"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/blog.write_tutorial_readme/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/causify-ai/helpers/blog.write_tutorial_readme"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/blog.write_tutorial_readme.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00745 |
| Opus 5.5 | $0.00004 | $0.00298 |
| Sonnet 5.5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade C, and why
blog.write_tutorial_readme scanned grade C with 2 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 1mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
> curl -LsSf https://astral.sh/uv/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> curl -LsSf https://astral.sh/uv/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Write clear, hands-on tutorials that help engineers quickly learn a new tool, technique, or concept
- Tutorials should be practical and immediately applicable, not theoretical surveys
Audience
- Target: Software engineers and technical practitioners
- Skill level: General to intermediate (some programming knowledge assumed)
- Goal: Enable readers to use the tool/technique effectively after reading
Tutorial Structure
-
Follow this outline:
-
Introduction (1-2 paragraphs)
- What is this tool/concept?
- Why should engineers care? (What problem does it solve?)
- When to use it (not just "always")
- What are other tools that solve similar problems
- Links to official docs
- Installation
- Documentation
- Tutorial
-
Prerequisites (if any)
- Required knowledge or tools
-
Installation/Setup (if applicable)
- Clear, copy-paste ready commands
- Verify installation with a simple test
-
Core Concepts (1-2 paragraphs)
- Explain 2-3 key ideas
-
Guidelines
Length
- Target: 10-15 minutes reading time (roughly 1500-2500 words)
- Avoid: Overly long tutorials that cover everything; focus on the 80% use case
Template
- Use
website/docs/blog/posts/draft.blog_template.mdas template
Code Examples
- Use copy-paste ready code blocks with
bashor language-specific syntax highlighting - Include expected output so readers know it worked
- For shell commands, show the prompt style, e.g.,
- On macOS and Linux using the official installer:
> curl -LsSf https://astral.sh/uv/install.sh | sh
- On macOS and Linux using the official installer:
Platform Coverage
- Focus on macOS and Linux instructions
Tone & Voice
- Direct and practical ("use this when..." not "one might consider...")
- Active voice, short sentences
- Assume readers are busy engineers
- Don't be overly casual
Visuals
- Include diagrams only if they clarify workflow or architecture
- Use simple diagrams using mermaid, graphviz, or reference external images if needed
- Don't over-decorate
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.
- 1mo ago Changed · +6 lines · -11 tokens per session a2157e5986d5
- 1mo ago First seen · 93 lines · 22 tokens per session scan C e900370eb7cc
blog.write_tutorial_readme is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 745 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.