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/tsitsishvili/documentator/documentator-api-docsnpx skills add tsitsishvili/documentator --skill documentator-api-docsgit clone --depth 1 https://github.com/tsitsishvili/documentatorWhat 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.00107 | $0.02707 |
| Opus 5 | $0.00053 | $0.01354 |
| Sonnet 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 2d 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.
- 2d 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 21d ago), licensed MIT. It adds 107 tokens to every session and 2,707 once invoked, about $0.0005 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-30.
Other skills, from other repositories
wiki_submit
Submit wiki documentation pages to Wegent backend API. Simplifies the HTTP POST process for wiki content submission.
developer-marketing-playbook
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
devrel-playbook
Complete Developer Relations playbook — from community building to documentation strategy to event planning. Covers Discord/Slack management, conference speaking, hackathon sponsorship, and measuring DevRel ROI. By @WeiYipei.
api-guide
Guide for implementing REST and GraphQL APIs (create, get, search, update, delete, purge, scope prefix patterns, admin prefix, SearchScope, BaseFilterAdapter, @apifunction, Click CLI).
bai-cli
./bai v2 CLI usage for testing/verifying API endpoints and managing resources — entity-command reference, login/config, search patterns, testing workflow (REST API client, NOT the v1 backend.ai CLI).
bep-guide
Guide for writing and managing BEPs (Backend.AI Enhancement Proposals) - creation workflow, document segmentation, context-for-ai blocks, Decision Log.