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 tsitsishvili/documentator --skill documentator-api-docsgit clone --depth 1 https://github.com/tsitsishvili/documentatorWrote 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/tsitsishvili/documentator/documentator-api-docs)<a href="https://agentmods.dev/skills/tsitsishvili/documentator/documentator-api-docs"><img src="https://agentmods.dev/badge/skills/tsitsishvili/documentator/documentator-api-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/tsitsishvili/documentator/documentator-api-docs"><img src="https://agentmods.dev/badge/skills/tsitsishvili/documentator/documentator-api-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.00107 | $0.02707 |
| Opus 5.5 | $0.00043 | $0.01083 |
| Sonnet 5.5 | $0.00021 | $0.00541 |
| Haiku 4.5 | $0.00011 | $0.00271 |
Grade A, and why
documentator-api-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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build self-documenting Laravel endpoints
Generate accurate native OpenAPI 3.2 through application code, with an explicit 3.1 compatibility projection when downstream tooling needs it. Prefer inference from idiomatic Laravel; add Documentator attributes only for facts the code cannot express or inference cannot see. Treat an attribute as an intentional last-write-wins override.
Follow the endpoint workflow
1. Inspect the complete endpoint
Read these sources before editing:
config/documentator.php, especially route matching/exclusions, auth, grouping, status inference, error responses, examples, and extensions.- The route definition and middleware.
- The controller method, invokable action, or closure and its PHPDoc.
- The FormRequest, inline validation, request accessors, or Data input.
- The Resource, Data object, model, return type, and readable return expressions.
- Existing feature tests and any committed OpenAPI contract.
Confirm the route URI matches documentator.routes.match and is not matched by
routes.exclude, routes.exclude_middleware, or #[Hidden].
2. Assign one source to each fact
Decide where each fact belongs:
| Fact | Preferred source |
|---|---|
| Method and URI | Laravel route |
| Summary and description | Method/closure docblock |
| Path input | Route placeholder, constraint, or model binding |
| URI query input | Request accessor, GET/HEAD validation, Spatie Query Builder, or #[QueryParam] |
| Request content | FormRequest, inline validation, Data input, or #[BodyParam] |
| Success schema | Return type/expression, Resource/Data/model, or #[Response] |
| Auth | Middleware/config, global auth, or #[Authenticated] |
| Group/version | Config/controller inference or #[Group] |
| Visibility/lifecycle | #[Hidden] / #[Deprecated] |
| Callback/webhook/stream | #[Callback], #[Webhook], or #[Response(stream: true)] |
Avoid describing the same fact twice unless the attribute deliberately corrects an inferred value.
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 · 310 lines · 107 tokens per session scan A 15c314cab839
documentator-api-docs is a skill published in the GitHub repository tsitsishvili/documentator (17 stars, last pushed 5d ago), licensed MIT. It adds 107 tokens to every session and 2,707 once invoked, about $0.0004 per session on Opus 5.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-30.
Other skills, from other repositories
api-documentation-v2
API Documentation Workflow workflow skill. Use this skill when the user needs API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging…
api-documentation
API Documentation Workflow workflow skill. Use this skill when the user needs API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging…
openapi-expert
Expert-level OpenAPI/Swagger specification for API design, documentation, and code generation. Use when the user mentions swagger, API specs, REST, API design, or documentation, or when the task involves OpenAPI Specification, Webhooks, or Polymorphism.
api-documenter-v2
This public intake copy packages plugins/antigravity-awesome-skills/skills/api-documenter from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
api-documentation
Best practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.
api-documentation-generator-v2
API Documentation Generator workflow skill. Use this skill when the user needs Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices and the operator should preserve the upstream workflow, copied support files, and provenance before…