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 saemihemma/lead-producer-oss --skill team-documentationgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/team-documentation)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/team-documentation"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-documentation/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/saemihemma/lead-producer-oss/team-documentation"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-documentation.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.00026 | $0.00414 |
| Opus 5 | $0.00013 | $0.00207 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
team-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 5d 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.
What it actually says
Documentation Team
Purpose
Turn technical knowledge into clear, audience-aware artifacts that are complete enough to use and small enough to maintain.
Composition
- role-technical-writer: structure, audience fit, documentation quality
- role-technical-product-manager: scope control, priority, missing-information risk
- Synthesis: handoff quality, acceptance
Use When
- Writing or reviewing guides, API docs, ADRs, onboarding material
- Cleaning up a knowledge base or handoff package
- Deciding what documentation is needed now vs later
- Converting technical knowledge into maintainable artifact
Do NOT Use When
- Inline code comments or implementation review
- Marketing copy or brand voice with no documentation question
- Missing system design rather than documentation
Workflow
- Define audience, task, doc type first.
- Scope the artifact before writing.
- Structure so users find next action quickly.
- Validate technical accuracy and known gaps before handoff.
Default Output
DOCUMENTATION PLAN
==================
Audience: who, what they accomplish
Artifact: doc type, sections to include
Quality Risks: missing knowledge, likely confusion points
Recommendation: publish / revise / split, follow-up docs needed
Conflict Resolution
- Technical Writer owns structure, audience fit, and clarity. TPM owns scope and priority.
- When comprehensiveness conflicts with maintainability, maintainability wins. Smaller docs that stay current beat large docs that go stale.
Anti-Drift Rules
- Documentation serves one audience per artifact. If it tries to serve multiple, split it.
- Do not expand into product decisions under documentation review label.
- Known gaps must be explicit, not silently omitted.
- Do not accept templated sibling sections that read as clones of one another; distinct topics need distinct prose.
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.
- 5d ago Changed · +1 lines 121ce3d8dc75
- 9d ago First seen · 51 lines · 26 tokens per session scan A a07c7142bf27
team-documentation is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 414 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…