Borrowing it
Nothing to install: this file belongs to thunder-id/thunderid. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thunder-id/thunderid/main/.agent/skills/docs/SKILL.mdgit clone --depth 1 https://github.com/thunder-id/thunderidWrote 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/thunder-id/thunderid/docs)<a href="https://agentmods.dev/skills/thunder-id/thunderid/docs"><img src="https://agentmods.dev/badge/skills/thunder-id/thunderid/docs/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/thunder-id/thunderid/docs"><img src="https://agentmods.dev/badge/skills/thunder-id/thunderid/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01048 |
| Opus 5.5 | $0.00000 | $0.00419 |
| Sonnet 5.5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
docs 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ThunderID Documentation Skill
One skill for every documentation task, split into reference files so only the relevant one loads into context. This file is a dispatch table, not the rules themselves — the actual instructions live in the reference file(s) below.
If the target path is a SKILL.md under .agent/skills/ or .claude/skills/, stop for every action below: these are agent instructions, not documentation, and none of these rules apply.
Step 1: Match the request to a reference file
Explicit form
If invoked as /docs <action> [file-path], or the request plainly names one of these action words, map directly with no further interpretation:
| action | reference |
|---|---|
new-page |
new-page.md |
edit |
edit.md |
check |
check.md |
style |
style.md |
tech |
tech.md |
api |
api.md |
seo |
seo.md |
review |
review.md |
use-case |
use-case.md |
diagram |
diagram.md |
Natural-language form
Otherwise, match the request's intent:
| The user is asking to... | Read |
|---|---|
| Create a new page, or "write docs for X" when nothing covers the topic yet | new-page.md |
| Write or fill in content on an existing page (a placeholder, a gap, a new section) | edit.md |
| Check, lint, or verify structural standards (frontmatter, headings, links, sidebar registration, etc.) | check.md |
| Review writing quality, tone, AI-sounding prose, voice consistency | style.md |
| Verify technical accuracy (protocol/API/SDK/config/security claims) | tech.md |
Review an OpenAPI spec (api/*.yaml) or an SDK API reference page (docs/content/sdks/*/apis/**) for consistency/accuracy |
api.md |
| Check SEO / discoverability | seo.md |
| Run the full pre-merge review (structure + style + tech together) | review.md |
| Review my changes / review the diff / review before I open a PR, no file named | review.md (diff mode — reads every changed file, including uncommitted, instead of one named file) |
Structure or audit a use-case section (docs/content/use-cases/<pattern>/): page order, diagram design, jargon literacy, scoring rubric |
use-case.md |
| Author or design any Mermaid diagram: pick the type (sequence, flowchart, architecture, state), gather the real steps/components, construct and confirm, or debug why one looks wrong | diagram.md |
What ships with it
10 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.
- 1mo ago First seen · 61 lines · 0 tokens per session scan A 54780fc2f598
docs is a skill published in the GitHub repository thunder-id/thunderid (594 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,048 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-30.
Other skills, from other repositories
coding-directives
Implement or review caddy-security Go code, Caddy modules, parsers, lifecycle, and HTTP delegation. Use for app/plugin boundaries, authcrunch integration, errors, logging, and code conventions.
jwt
Development guide for the jwt JSON Web Token library for Go (github.com/kataras/jwt). Use this skill when signing or verifying JWTs, choosing a signing algorithm (HMAC, RSA, RSA-PSS, ECDSA, EdDSA), reading or validating standard or custom claims, setting expiry and clock-skew tolerance, rotating keys with a kid-based…
configuration-authentication-cookies
Configure portal cookie names, prefixes, domains, paths, attributes, and refresh overrides. Use for cookie precedence and coordination with authorization token discovery.
configuration-authorization
Configure authorization policies, ACLs, static claims enrichment, required external decisions, bypasses, identity headers, JWT verification, remote Basic/API-key auth, SQLite/Consul API keys, and direct OAuth without a portal.
authentication-portal-api
Build or troubleshoot portal JSON/native login clients, refresh, Documents, profile and admin APIs, and public JWKS. Use for HTTP contracts; portal Caddyfile wiring belongs to configuration-authentication.
configuration-http-integrations
Mount authenticate and authorize handlers, separate portal and protected routes, align auth URLs, and preserve trusted proxy metadata. Use for path conflicts, split hosts, public JWKS, and route ordering.