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 ivegamsft/basecoat --skill documentationgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/documentation)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/documentation"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/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/ivegamsft/basecoat/documentation"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/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.00079 | $0.00422 |
| Opus 5 | $0.00039 | $0.00211 |
| Sonnet 5 | $0.00016 | $0.00084 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
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 today.
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 Skill
Use this skill when the task involves creating, updating, or reviewing technical documentation of any kind.
When to Use
- Creating a new README or project overview
- Recording an architecture decision (ADR)
- Writing an operational runbook
- Reviewing existing docs for accuracy and completeness
- Establishing documentation standards for a project
- Writing API reference documentation
How to Invoke
Reference this skill by attaching skills/documentation/SKILL.md to your agent context, or instruct the agent:
Use the documentation skill. Apply the ADR template to document our decision to adopt PostgreSQL.
Templates in This Skill
| Template | Purpose |
|---|---|
readme-template.md |
Project README structure — overview, setup, usage, and contributing |
adr-template.md |
Architecture Decision Record — context, decision, and consequences |
runbook-template.md |
Operational runbook — trigger, steps, rollback, and escalation |
Agent Pairing
This skill is designed to be used alongside the following agents:
- tech-writer — Drives documentation creation using these templates
- solution-architect — Provides architectural context for ADRs
- devops-engineer — Provides operational context for runbooks
- product-manager — Provides feature context for user-facing documentation
For code-level documentation (inline comments, docstrings), coordinate with the backend-dev or frontend-dev agents.
What ships with it
4 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.
- today First seen · 50 lines · 79 tokens per session scan A b543470a2338
documentation is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 422 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-09-08.
Other skills, from other repositories
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
api-rate-limit-handler
Implement bounded, idempotency-aware API throttling, backoff, and retry handling for 429 and transient 5xx responses.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
Developmental Gene Panel Design Workflow
Panel design for DEVELOPING / dynamic systems (embryonic organs, differentiation, regeneration). The target experiment is usually a LATE / terminal stage, but the biology is a trajectory: terminal cell types are end-products of earlier lineage programs. A panel built from the target stage alone resolves terminal…
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.