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 agents/jeremylongworth-source/agentskills/agents.technical-documentationgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/agents/jeremylongworth-source/agentskills/agents.technical-documentation)<a href="https://agentmods.dev/agents/jeremylongworth-source/agentskills/agents.technical-documentation"><img src="https://agentmods.dev/badge/agents/jeremylongworth-source/agentskills/agents.technical-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.00000 | $0.00248 |
| Opus 5 | $0.00000 | $0.00124 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
AGENTS.technical-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 3d 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
Use local skills as the primary routing layer for technical documentation work.
Use readme-upgrade when improving README positioning, install steps, examples,
validation, roadmap, and contribution guidance.
Use api-doc-writing when documenting endpoints, SDK methods, schemas, auth,
errors, rate limits, examples, and OpenAPI-style contracts.
Use release-notes for user-facing release notes and changelog-maintenance
for historical CHANGELOG updates and Unreleased/version sections.
Use architecture-docs when documenting system structure, module boundaries,
data flow, dependencies, decisions, tradeoffs, or ADRs.
Use migration-guide when users need to move between versions, APIs, hosts,
setups, or workflows.
Use developer-onboarding for local setup, first-run verification, repo
orientation, common workflows, and contribution paths.
Use tutorial-writing for task-focused walkthroughs, quickstarts, how-to
guides, and learning paths.
Use concise-technical-writing to tighten docs while preserving technical
accuracy.
Verify commands, links, compatibility claims, and version names before documenting them. Keep host-specific setup in setup docs when the portable workflow should remain vendor-neutral.
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.
- 3d ago First seen · 30 lines · 0 tokens per session scan A 4ef6b4b6c1fc
AGENTS.technical-documentation is an agent published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 tokens. 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 agents, from other repositories
github.awesome-copilot.agents
MCP server that suggests repository-specific AI agent skills.
dotnet.skills.plugins.dotnet-test.agents
MCP server that suggests repository-specific AI agent skills.
runceel.ai-dev-template..github.agents
MCP server that suggests repository-specific AI agent skills.
addyosmani.agent-skills.agents
MCP server that suggests repository-specific AI agent skills.
dotnet.skills.plugins.dotnet-diag.agents
MCP server that suggests repository-specific AI agent skills.
garrytan.gstack.agents
MCP server that suggests repository-specific AI agent skills.