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 tranhieutt/software_development_department --skill skill-technical-documentgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/skill-technical-document)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/skill-technical-document"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/skill-technical-document/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/tranhieutt/software_development_department/skill-technical-document"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/skill-technical-document.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.00115 | $0.01280 |
| Opus 5 | $0.00057 | $0.00640 |
| Sonnet 5 | $0.00023 | $0.00256 |
| Haiku 4.5 | $0.00012 | $0.00128 |
Grade A, and why
skill-technical-document 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 8d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
Generate a single, self-contained .html file that looks and feels like
hooks_visual_report.html — warm off-white palette, JetBrains Mono + Inter
fonts, fixed sidebar with section nav, and layered content sections —
without needing any external CSS framework or JS library.
Instructions
Step 1: Identify document type
Pick the layout template based on content:
| Document type | Primary component | Secondary components |
|---|---|---|
| Hook / agent reference | Hook-table | Deployment priority list |
| Architecture / flow | Diagram-block | Section tables |
| Audit / compliance | Matrix-table | Callouts, checklists |
| ADR / decision record | Priority-list | Callouts, diagram |
| Memory / config reference | Hook-table | Callouts |
Step 2: Plan sections (max 7)
Map content → § 00, § 01, ... sections. Each section needs:
- A unique
idfor the sidebar anchor - A
section-numlabel - A
section-desc(1–2 sentences) - One primary component (table, diagram, or list)
Step 3: Assign nav dot colors
Nav dots communicate semantics, not decoration:
green→ start/lifecycle/sessionred→ security/blocking/guardblue→ enrichment/context/read-pathpurple→ observability/logging/audit- (no class) → neutral (matrix, summary, deployment order)
Step 4: Write content following these rules
For table cells (col-desc):
- Lead with
<strong>Bold summary sentence.</strong>— one sharp phrase - Follow with detail text
- Bullet points go inside
<ul class="behaviors">— never plain<ul> - Inline code uses
<code>inside.col-desc
For hook/agent names (hn):
- Always monospace
- Never truncate — use full filename including extension
For numbers in doc-meta:
- Must be real, meaningful counts (files, hooks, layers, date)
- Don't invent stats
For event badges:
- SessionStart →
.ev-green - PreToolUse:Bash/Task (when it can
exit 2) →.ev-red+ add<span class="blocks">blocks</span> - UserPromptSubmit, PreToolUse:Read/Write →
.ev-blue - PostToolUse, SubagentStart, PreCompact →
.ev-purple - Stop, sub-process, utility →
.ev-orange - Warnings/partial states →
.ev-amber
What ships with it
2 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.
- 8d ago First seen · 132 lines · 115 tokens per session scan A dde54d4dcd96
skill-technical-document is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 115 tokens to every session and 1,280 once invoked, about $0.0006 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-03.
Other skills, from other repositories
reviewing-docs
Use when the user has a finished or near-finished document (memo, business review, PRD, decision doc, briefing, comms, framework, talking points, post-mortem) and wants it pressure-tested before it ships, such as "review this doc", "poke holes in this", "is this ready to send". Works on any doc, not just…
ingest
Turn whatever the human has — a PDF, a link, a DOI, a screenshot of a citation — into raw/ sources this project can compile.
brochure-generator
Generates premium, multi-page, mobile-optimized (1:1 aspect ratio) PDF marketing brochures for exclusive retreats, workshops, luxury events, or any high-end product/service offering. Use this skill whenever a user asks to create a brochure, marketing PDF, event flyer, WhatsApp marketing material, social media…
venue-templates
Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Use when selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.
google-drive
Interact with Google Drive - search files, find folders, list contents, download files, upload files, create folders, move, copy, rename, and trash files. Use when user asks to: search Google Drive, find a file/folder, list Drive contents, download or upload files, create folders, move files, or organize Drive…
sync-submission
Audit SSOT-to-submission drift and create journal submission manifests from canonical manuscript artifacts.