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 agentmods add skills/tahirraufkeeyu/software-development-agent-stack--sdas/documentationnpx skills add tahirraufkeeyu/software-development-agent-stack--sdas --skill documentationgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/documentation)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/documentation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/documentation.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.02293 |
| Opus 5 | $0.00034 | $0.01146 |
| Sonnet 5 | $0.00013 | $0.00459 |
| Haiku 4.5 | $0.00007 | $0.00229 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- "Write a README for this repo."
- "Generate API docs from the OpenAPI spec" or "from these route files".
- "Write an ADR for choosing Kafka over SQS."
- "Produce a CHANGELOG entry for v1.4.0."
- "Document this module / this CLI command."
Do not use this skill for marketing copy, blog posts, or long-form narrative — those are outside its scope.
Inputs
The artifact type — one of:
readmeapi-docsadrchangelogmodule-docrunbook
Plus inputs specific to the type (see Procedure).
Outputs
Markdown files placed at the repo's conventional location:
README.mdat repo root.docs/adr/NNNN-title.mdfor ADRs (sequential zero-padded number).CHANGELOG.mdat repo root (Keep a Changelog format).docs/api/for API reference.docs/runbooks/<service>.mdfor runbooks.docs/modules/<name>.mdfor module-level docs.
Tool dependencies
- Read, Grep, Glob for codebase inspection.
- Bash for
git log,git tag,git diff. - Optional:
openapi-cli/redoclyto render OpenAPI.
Procedure
README
- Detect the project shape: languages (by file extensions), build tool (
package.json,pyproject.toml,go.mod,Cargo.toml,Makefile), entry points, Dockerfile, CI config. - Extract the one-sentence purpose from the existing top of
README.mdif present, fromdescriptionin the manifest, or from a repo description. If none, ask the user. - Draft sections in this order:
- Title + one-sentence description.
- Status badges (CI, coverage, license, latest release) — only ones that actually exist.
- Quickstart: the three commands that take a new developer from clone to "it runs" (install, build/test, run). Verify commands by inspecting scripts; do not invent.
- Usage: the two or three most common invocations with real examples.
- Configuration: table of env vars with purpose, default, required-ness (read from
.env.example, config schema, or source). - Development: test command, lint command, format command, pre-commit setup.
- Deployment: link to runbook or pipeline if present.
- Contributing: link to
CONTRIBUTING.mdif present; otherwise a short block (branch naming, commit style, PR review expectations). - License: one line, name and link.
- Keep the README under ~200 lines. Push depth to
docs/.
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 First seen · 271 lines · 67 tokens per session scan A b600c0cb85d7
documentation is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 2,293 once invoked, about $0.0003 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-30.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…