Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add andreymudri/claude-teammates/plugin install claude-teammatesWrote 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/andreymudri/claude-teammates/writing-skills)<a href="https://agentmods.dev/skills/andreymudri/claude-teammates/writing-skills"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/writing-skills/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/andreymudri/claude-teammates/writing-skills"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/writing-skills.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.00021 | $0.01561 |
| Opus 5 | $0.00010 | $0.00781 |
| Sonnet 5 | $0.00004 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
writing-skills 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Skills
Adapted from the MIT-licensed superpowers plugin by Jesse Vincent. See NOTICE.md.
Overview
Writing a skill is Test-Driven Development applied to process documentation. Watch an agent fail without the skill (baseline), write the skill, then watch a fresh agent comply. If you never watched the failure, you don't know whether the skill teaches the right thing — or whether there was anything to teach at all.
A skill is a reusable technique, pattern, or reference — not a narrative about how you solved something once. Don't create one for a one-off fix or a project-specific convention (put that in the project's own instructions file instead).
Start from the template
Copy templates/SKILL.template.md as the starting structure for a new skill. It carries the
required frontmatter shape and the section skeleton (When to use / Process / Red flags) —
fill it in rather than improvising frontmatter from scratch.
Rules this plugin's test suite enforces
These are checked mechanically by tests/skills.test.mjs and tests/skill-contracts.test.mjs
on every skill under skills/ — get them wrong and the suite fails, not just a reviewer:
namematches the containing folder exactly.skills/writing-skills/SKILL.mdmust declarename: writing-skills.descriptionstarts withUse when. It states triggering conditions, not what the skill does — see "Write the description as a trigger" below.- Every CLI subcommand named in the body must actually exist. Only
init-run,gate,digest,claim,unclaim, andworkfloware real subcommands of the CLI entrypoint. Naming a subcommand that doesn't exist fails the suite, not just the reader. - Every
tm-*agent named in the body must actually exist. Onlytm-implementer,tm-reviewer, andtm-integratorexist underagents/. - The CLI is always invoked through
$CLAUDE_PLUGIN_ROOT, never a relative path:node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" <subcommand> --root <project root>. A relative invocation works from the author's shell and breaks for everyone else.
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.
- 12d ago First seen · 127 lines · 21 tokens per session scan A e91f8f56cfed
writing-skills is a skill published in the GitHub repository andreymudri/claude-teammates (2 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 1,561 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.