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/blendsdk/claude-codeops/techdocsnpx skills add blendsdk/claude-codeops --skill techdocsgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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.00195 | $0.02726 |
| Opus 5 | $0.00097 | $0.01363 |
| Sonnet 5 | $0.00039 | $0.00545 |
| Haiku 4.5 | $0.00019 | $0.00273 |
Grade A, and why
techdocs 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 yesterday.
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
techdocs — Technical Architecture Documentation
CodeOps Skills Version: 3.20.0
Create and maintain a living, VitePress-compatible technical architecture documentation set in
the project's docs/ directory, capturing accumulated design knowledge across requirements and
planning phases. The body branches by phrasing and arguments:
| Phrasing / argument | Mode | Action |
|---|---|---|
make_techdocs, "document the architecture", "create architecture docs" |
Create / regenerate | Phases 1–6: comprehensive create or full regeneration |
make_techdocs --continue |
Resume | Pick up an interrupted authoring session (see Session resume) |
review_techdocs, "review the techdocs", "health check the docs" |
Health check | 7-dimension diagnostic report (no file changes) |
| (auto) exec_plan phase complete | Incremental | Add ADRs / update changed sections only |
| (auto) exec_plan plan complete | Comprehensive | Full pass over every section vs. codebase |
| (auto) make_requirements complete | Incremental | New design decisions → ADRs |
What this is (and is NOT)
| In scope — TECHNICAL docs (this skill) | Out of scope — PRODUCT docs |
|---|---|
| Architecture, design decisions, data models, API contracts, infrastructure, security | End-user guides, tutorials, FAQ, release notes, marketing |
| Developer onboarding, dev workflow, deployment procedures | Feature announcements, user-facing changelogs |
Product documentation is a separate concern. If the project needs user-facing docs, the user
should request them explicitly. They live elsewhere (e.g. docs/product/) and are NOT governed
by this skill.
Opt-in, then auto-update
Technical documentation is not mandatory by default, but once opted in it is automatically maintained.
The opt-in marker
The presence of docs/index.md with this frontmatter marker means techdocs are active:
---
techdocs: true
---
If docs/index.md exists but lacks this marker, it is NOT a techdocs-managed file — do not
auto-update it.
What ships with it
3 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.
- yesterday First seen · 206 lines · 195 tokens per session scan A 4b4338d15812
techdocs is a skill published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 195 tokens to every session and 2,726 once invoked, about $0.0010 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…