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 tale-project/tale --skill write-docsgit clone --depth 1 https://github.com/tale-project/taleWrote 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/tale-project/tale/write-docs)<a href="https://agentmods.dev/skills/tale-project/tale/write-docs"><img src="https://agentmods.dev/badge/skills/tale-project/tale/write-docs/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/tale-project/tale/write-docs"><img src="https://agentmods.dev/badge/skills/tale-project/tale/write-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 69 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 71 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 73 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00079 | $0.01635 |
| Opus 5.5 | $0.00032 | $0.00654 |
| Sonnet 5.5 | $0.00016 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
write-docs 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 16d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write documentation people can use
Help the reader make progress from the situation they are in. A newcomer needs a guided first success; an experienced user needs the missing step; an administrator needs consequences and permissions; a developer needs exact inputs and outputs. Support these needs with connected pages, not one page that assumes every reader has the same knowledge.
Discover before drafting
Read the repo contract, the guide nearest the docs tree, the renderer's component registry, and
the checks for that content. Tale has two content trees: docs/AGENTS.md governs the EN/DE/FR
product guides, while the design-system authoring contract
governs the English component guides and their live demos. Use the contract for the tree you edit.
Find the existing owner of the topic and its neighboring pages before adding another explanation.
Use the applicable locale’s resolved message catalogs for visible UI labels; shared controls may
read @tale/ui or @tale/marketing-ui catalogs beneath the service’s overrides.
In the task's planning note outside the clone, record:
- Reader, goal, starting knowledge, and the page's job: tutorial, how-to, explanation, reference, troubleshooting, or navigation.
- Current gaps and the facts that need checking: role, prerequisites, route, inputs, defaults, limitations, result, and recovery.
- Existing content to reuse or link, worthwhile visuals/examples, and affected locales and links.
Keep the note proportional to the change. Reuse an existing task note; no separate notes skill is required. For a broad overhaul, map readers to their core tasks and record coverage and verification status. Page count and word count are not measures of completeness.
Establish the facts
Drive the real UI before describing a workflow. Use a disposable, seeded local organization when available. Follow the documented starting point through the result; inspect relevant empty, loading, permission, and failure states. Check keyboard access for the controls you describe. Source and tests clarify hidden defaults, limits, and persistence; they do not replace using the UI. A delegated observer may provide a concrete route/action/result record with the relevant version.
What ships with it
5 files 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.
- 16d ago Changed · +17 tokens per session e9a4a5e30273
- 1mo ago Changed · -10 lines · -136 tokens per session 38ba1f46204c
- 1mo ago First seen · 133 lines · 198 tokens per session scan A 3fb27502e263
write-docs is a skill published in the GitHub repository tale-project/tale (35 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,635 once invoked, about $0.0003 per session on Opus 5.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
migrate-from-ai-sdk
Use when porting an app from the Vercel AI SDK (ai, @ai-sdk/) to @deuz-sdk/core. Triggers include "migrate from the AI SDK", "replace ai with @deuz-sdk/core", "we use streamText/generateText/useChat and want to switch", removing @ai-sdk/openai or @ai-sdk/anthropic, porting a toUIMessageStreamResponse route, converting…
pn-rag-evaluation
Evaluate retrieval-augmented generation pipelines — golden sets, automated metrics (incl. RAGAS-style), human rubrics, regression gates in CI. Use when building or changing RAG (chunks, embeddings, rerankers, prompts) and need quality proof, not vibes.
ai-product
Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.
domain_aircraft
Domain guidance for monitoring unmanned aircraft, covering the combined picture of airspace activity and alerts tied to time, location, and sensor sources.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.