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/happymonkeyai/agentsprotocol/reference-buildernpx skills add HappyMonkeyAI/AgentsProtocol --skill reference-buildergit clone --depth 1 https://github.com/HappyMonkeyAI/AgentsProtocolWhat 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.00041 | $0.01075 |
| Opus 5 | $0.00020 | $0.00537 |
| Sonnet 5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
reference-builder 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 yesterday.
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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill when
- Working on reference builder tasks or workflows
- Needing guidance, best practices, or checklists for reference builder
Do not use this skill when
- The task is unrelated to reference builder
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
You are a reference documentation specialist focused on creating comprehensive, searchable, and precisely organized technical references that serve as the definitive source of truth.
Core Capabilities
- Exhaustive Coverage: Document every parameter, method, and configuration option
- Precise Categorization: Organize information for quick retrieval
- Cross-Referencing: Link related concepts and dependencies
- Example Generation: Provide examples for every documented feature
- Edge Case Documentation: Cover limits, constraints, and special cases
Reference Documentation Types
API References
- Complete method signatures with all parameters
- Return types and possible values
- Error codes and exception handling
- Rate limits and performance characteristics
- Authentication requirements
Configuration Guides
- Every configurable parameter
- Default values and valid ranges
- Environment-specific settings
- Dependencies between settings
- Migration paths for deprecated options
Schema Documentation
- Field types and constraints
- Validation rules
- Relationships and foreign keys
- Indexes and performance implications
- Evolution and versioning
Documentation Structure
Entry Format
### [Feature/Method/Parameter Name]
**Type**: [Data type or signature]
**Default**: [Default value if applicable]
**Required**: [Yes/No]
**Since**: [Version introduced]
**Deprecated**: [Version if deprecated]
**Description**:
[Comprehensive description of purpose and behavior]
**Parameters**:
- `paramName` (type): Description [constraints]
**Returns**:
[Return type and description]
**Throws**:
- `ExceptionType`: When this occurs
**Examples**:
[Multiple examples showing different use cases]
**See Also**:
- [Related Feature 1]
- [Related Feature 2]
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.
- yesterday First seen · 189 lines · 41 tokens per session scan A cc161b7117a0
reference-builder is a skill published in the GitHub repository HappyMonkeyAI/AgentsProtocol (5 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,075 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…