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 AuraVixStudio/caelo --skill document-codegit clone --depth 1 https://github.com/AuraVixStudio/caeloWrote 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/auravixstudio/caelo/document-code)<a href="https://agentmods.dev/skills/auravixstudio/caelo/document-code"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/document-code/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/auravixstudio/caelo/document-code"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/document-code.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.00017 | $0.00241 |
| Opus 5.5 | $0.00007 | $0.00096 |
| Sonnet 5.5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
Document code 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.
What it actually says
Document code
Use this to make code understandable to the next reader.
Steps
- Understand first. Read the code until you can explain what it does and why. Don't document guesses.
- Docstrings. Add/update docstrings on public functions, classes and modules: purpose, parameters, return value, and non-obvious behavior or side effects. Match the project's docstring style.
- Comments where they earn their place. Explain why (intent, trade-offs, gotchas), not what the code already says. Remove stale comments.
- External docs. If the change affects usage, update the README / API docs / module header accordingly.
- Report. Note what you documented and anything still unclear that needs an owner.
Notes
- Keep comment density consistent with the surrounding file.
- User-facing docs follow the repo's language rule; internal comments follow the file.
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 · 28 lines · 17 tokens per session scan A 324329592307
Document code is a skill published in the GitHub repository AuraVixStudio/caelo (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 17 tokens to every session and 241 once invoked, about $0.0001 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
skill-creator
A guide for creating and maintaining skills for Lfcode, including where to store them and which files each skill needs.
tavern-management
Use when the user asks to import or translate an Lfcode Tavern or SillyTavern character card or worldbook, including PNG image cards, or manage the Tavern plugin lifecycle.
error-collection
A structured record of confirmed engineering mistakes, their root causes, and checks that prevent them from returning. It uses evidence from real application behavior, not just successful builds.
playwright-browser
Use when controlling browser pages with Playwright MCP in Lfcode; guides navigation, screenshots, interaction, and reuse of hidden or collapsed embedded side browser targets instead of the Electron app shell.
accessibility-auditor
Use when the user asks to audit accessibility, keyboard usability, semantics, contrast, focus behavior, or assistive-technology support in a UI. Inspect the actual rendered page and interaction states, report evidence-backed findings, and only implement fixes when explicitly requested.
codebase-explorer
Use when the user asks to understand, map, trace, or locate behavior in an unfamiliar repository. Inspect the actual code, configuration, runtime entrypoints, and tests before proposing changes; stay read-only unless a change is explicitly requested, and report evidence and remaining uncertainty.