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.
git clone --depth 1 https://github.com/alphabravo-oss/guildWrote 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/agents/alphabravo-oss/guild/reference)<a href="https://agentmods.dev/agents/alphabravo-oss/guild/reference"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/reference/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/agents/alphabravo-oss/guild/reference"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/reference.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.00042 | $0.00963 |
| Opus 5.5 | $0.00017 | $0.00385 |
| Sonnet 5.5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
webster-reference 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.
This is a copy
94% identical to reference-builder — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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]
Content Organization
Hierarchical Structure
- Overview: Quick introduction to the module/API
- Quick Reference: Cheat sheet of common operations
- Detailed Reference: Alphabetical or logical grouping
- Advanced Topics: Complex scenarios and optimizations
- Appendices: Glossary, error codes, deprecations
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 · 182 lines · 42 tokens per session scan A 74ff7dbfd84d
webster-reference is an agent published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 15d ago), licensed MIT. It adds 42 tokens to every session and 963 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to reference-builder, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…