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 MatrixFounder/Agentic-development --skill documentation-standardsgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/documentation-standards)<a href="https://agentmods.dev/skills/matrixfounder/agentic-development/documentation-standards"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/documentation-standards/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/matrixfounder/agentic-development/documentation-standards"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/documentation-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 233 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.07834 |
| Opus 5.5 | $0.00007 | $0.03134 |
| Sonnet 5.5 | $0.00003 | $0.01567 |
| Haiku 4.5 | $0.00002 | $0.00783 |
Grade A, and why
documentation-standards 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 13d 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 — 529 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Purpose: Defines the non-negotiable standards for code comments, docstrings, and global artifacts.
1. Red Flags (Anti-Rationalization)
STOP if you are thinking:
- "I'll add comments later" -> WRONG. Undocumented code is technical debt from the moment it is written.
- "The code is self-documenting" -> WRONG. Code explains how; comments explain why.
- "Artifacts are optional, I can skip them entirely" -> WRONG. Artifacts are part of delivery quality;
.AGENTS.mdmust follow project memory policy. - "I'll put the full explanation in the table cell" -> WRONG. A table is a scanning device. Prose inside a cell destroys scanning and makes every row of that table churn on any edit. Cell = label; explanation goes below the table.
- "It's all one topic, so it's one paragraph" -> WRONG. Topic is not structure. A reader needs entry points: paragraphs, lists, headings. A 30-line block has none.
- "Line length doesn't matter, editors soft-wrap" -> WRONG.
git diffand review comments are line-granular. A 2000-character line means a one-word fix shows up as a whole-paragraph rewrite, and reviewers stop reading.
2. Docstrings & JSDoc
All classes and functions MUST have documentation.
Python
Use Google-style docstrings.
[!TIP] See
assets/templates/python_docstring.pyfor the format.
JavaScript / TypeScript
Use JSDoc standards.
[!TIP] See
assets/templates/jsdoc_template.tsfor the format.
3. Comments
- Why vs What: Explain the reason for logic, not the syntax.
- Work Tracking: Use
# T O D O:(Python) or// T O D O:(JS/TS) for future work.
4. Path & Reference Standards (CRITICAL)
- Relative Paths Only: When linking to internal files in Artifacts (PLAN.md, TASK.md), ALWAYS use relative paths.
- ✅
[Ref](src/main.py) - ✅
[.agent/skills/core.md](.agent/skills/core.md) - ❌
file:///Users/username/project/src/main.py - ❌
/Absolute/System/Path
- ✅
What ships with it
8 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.
- assets/templates/agents_md_template.md 220 B
- assets/templates/jsdoc_template.ts 239 B runs code
- assets/templates/python_docstring.py 245 B runs code
- examples/good_documentation.py 990 B runs code
- scripts/check_positional_refs.py 61 KB runs code
- scripts/check_skill_refs.py 14 KB runs code
- scripts/tests/__init__.py 0 B runs code
- scripts/tests/test_human_channel.py 17 KB runs code
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.
- 13d ago Changed · +52 lines f35572e7e913
- 1mo ago First seen · 477 lines · 17 tokens per session scan A 2ec1ea8be47d
documentation-standards is a skill published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 7,834 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-31.
Other skills, from other repositories
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
workflow
Perform any development work on the ambient-ui component. Full workflow instructions.
chimera-write-the-check-before-the-code
A criterion written after the implementation describes the implementation. Write the failing check first, watch it fail, then build.
Learn what defines effective BDD scenarios
Interactive guidance on writing complete, effective BDD scenarios for story-flow.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.
ap-policies
Attach a completion policy gate (shell check or judge-agent rubric) to a session or fan-in group so turn-end only passes when the gate is green, then optionally auto-commit pending human ack. Use when the user says "gate this session on tests passing", "attach a policy", "commit only if tests are green", "judge…