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 Claude-Code-Community-Ireland/claude-code-resources --skill documentation-standardsgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/documentation-standards)<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/documentation-standards"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/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/claude-code-community-ireland/claude-code-resources/documentation-standards"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/documentation-standards.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.00034 | $0.02794 |
| Opus 5.5 | $0.00014 | $0.01118 |
| Sonnet 5.5 | $0.00007 | $0.00559 |
| Haiku 4.5 | $0.00003 | $0.00279 |
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 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
README Template
Every project README should follow this structure. Omit sections that genuinely do not apply, but default to including them.
# Project Name
[][ci-link]
[][coverage-link]
[][npm-link]
[][license-link]
One-paragraph description of what this project does, who it is for,
and why it exists. Lead with the value proposition, not the technology.
## Table of Contents
- [Installation](#installation)
- [Quick Start](#quick-start)
- [Usage](#usage)
- [API Reference](#api-reference)
- [Configuration](#configuration)
- [Contributing](#contributing)
- [License](#license)
## Installation
### Prerequisites
- Node.js >= 18
- PostgreSQL >= 14
### Steps
npm install project-name
## Quick Start
Minimal working example — no more than 10 lines — that gets the
reader from zero to "it works."
## Usage
### Common Use Cases
Organize by task, not by API surface. Show the most common
workflows first.
### Advanced Usage
Edge cases, complex configurations, integration patterns.
## API Reference
Link to generated docs or inline the reference here.
## Configuration
| Variable | Default | Description |
|-----------------|-----------|------------------------------|
| `PORT` | `3000` | Server listening port |
| `DATABASE_URL` | — | PostgreSQL connection string |
## Architecture
Brief overview or link to architecture docs.
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md).
## License
[MIT](LICENSE) — see LICENSE file for details.
README Checklist
- Title matches the package/repo name exactly
- Description answers "what," "who," and "why" in one paragraph
- Installation steps are copy-pasteable and tested on a clean machine
- Quick Start example actually works — verify before merging
- Badges are live and point to correct URLs
- All links resolve (no 404s)
- Configuration table covers every environment variable
- License is explicitly stated and matches the LICENSE 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 · 419 lines · 34 tokens per session scan A 2955b0d93ffc
documentation-standards is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 2,794 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Fetches URLs and PDFs, then summarizes or returns clean Markdown; can also search the web through DeepSeek when built-in search is thin. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.