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 jimtin/production-ai --skill repo-technical-documentationgit clone --depth 1 https://github.com/jimtin/production-aiWrote 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/jimtin/production-ai/repo-technical-documentation)<a href="https://agentmods.dev/skills/jimtin/production-ai/repo-technical-documentation"><img src="https://agentmods.dev/badge/skills/jimtin/production-ai/repo-technical-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/jimtin/production-ai/repo-technical-documentation"><img src="https://agentmods.dev/badge/skills/jimtin/production-ai/repo-technical-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.00076 | $0.00959 |
| Opus 5 | $0.00038 | $0.00479 |
| Sonnet 5 | $0.00015 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
repo-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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Technical Documentation
Purpose
Use this skill to produce durable, repo-grounded technical documentation. The default output is split Markdown docs plus a machine-readable evidence file. Existing technical docs are updated in place when they exist; otherwise create the standard package under docs/repo-map/.
This is a documentation and inventory skill, not a remediation review. Use $full-app-review when the user wants prioritized findings or a fix plan.
Operating Rules
- Start from repo truth: applicable
AGENTS.md, tracked files, manifests, source entrypoints, tests, docs, configs, scripts, workflows, and deployment files. - Enumerate git-tracked files by default with
git ls-files. Consider every tracked file, but path-inventory only for secret-like, generated/build, binary, unreadable, or oversized files. - Never print or document secret values. Do not read
.env*, credential, token, private-key, local provider state, or similar files unless the user explicitly provides a safe fixture. - Tag every material claim as
confirmed,inferred,stale-doc, orunknown. Do not present inferred rationale as fact. - In Plan Mode or report-only requests, do not write docs. Return the proposed doc targets and update plan instead.
- Prefer updating existing technical docs over creating duplicate docs. If no suitable docs exist, create
docs/repo-map/. - Keep generated artifacts deterministic and repo-contained. Do not dirty unrelated tracked files.
Workflow
-
Baseline the repo.
- Read parent and repo-local instructions.
- Check
git status --short --untracked-files=all. - Identify existing technical docs, source roots, test roots, package managers, deployment targets, and canonical validation commands.
- Run this skill's helper,
scripts/repo_inventory.py <repo> --format json, resolved relative to this skill directory, for a deterministic first-pass fact inventory when useful.
-
Build the evidence map.
- Use
references/discovery-checklist.md. - Map API endpoints, UI routes, user actions, frameworks, libraries, data schemas, integrations, auth/roles, jobs, scripts, tests, deployment/runtime, observability, and docs.
- Record evidence as file paths, line references when inspected directly, manifest entries, config files, and test/doc references.
- Use
What ships with it
5 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.
- 10d ago First seen · 77 lines · 76 tokens per session scan A d5a34d8035c3
repo-technical-documentation is a skill published in the GitHub repository jimtin/production-ai (1 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 959 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-08-31.
Other skills, from other repositories
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
agent-safety
Use when bounding an LLM agent that already runs — scoping its task domain, gating tools to least privilege, defending against prompt injection in untrusted web/email/RAG text, requiring human approval on irreversible actions, capping runtime and cost, or triaging what it already did. NOT building the loop, tools, or…