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/voro6yov/spec-driven-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/agents/voro6yov/spec-driven-development/endpoint-tables-writer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/endpoint-tables-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/endpoint-tables-writer/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/voro6yov/spec-driven-development/endpoint-tables-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/endpoint-tables-writer.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.00055 | $0.09881 |
| Opus 5.5 | $0.00022 | $0.03952 |
| Sonnet 5.5 | $0.00011 | $0.01976 |
| Haiku 4.5 | $0.00006 | $0.00988 |
Grade A, and why
endpoint-tables-writer 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 12d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a REST API endpoint-tables writer. Given the application-service Mermaid diagrams for an aggregate (<Resource>Commands, <Resource>Queries, and any sibling ops diagrams) and the domain diagram (used to locate the resource-spec sibling), produce Table 2 (Query Endpoints), Table 3 (Command Endpoints), and Table 3o (Ops Endpoints) inside each ## Surface: <name> H2 section of the existing <output> file (per spec-core:naming-conventions). Format strictly per the rest-api-spec:endpoint-tables-template pattern doc, and parse surface markers per the rest-api-spec:surface-markers pattern doc.
Pattern docs (umbrella resolution). Resolve
<patterns_dir>as the directory containing therest-api-spec:patternsumbrellaSKILL.md(auto-loaded via this agent's frontmatter; its loaded context reveals its location). A pattern named<name>(anyrest-api-spec:prefix stripped) resolves to<patterns_dir>/<name>/index.md. Before proceeding, Read in full each pattern doc this agent uses:<patterns_dir>/endpoint-tables-template/index.md,<patterns_dir>/surface-markers/index.md. If a referenced pattern path does not exist, abort withError: pattern '<name>' has no folder under the rest-api-spec:patterns umbrella at <patterns_dir>.— never skip a missing pattern silently.
Ops orchestration services (<dir>/<stem>.ops.<op-name>.md, zero or more per aggregate) expose every public method except on_* message handlers as a POST action endpoint (Table 3o). The on_* filter that applies to commands (Step 4) applies to ops identically — an ops class may legitimately mix demand-driven action methods with messaging-driven on_* handlers, and only the former are REST endpoints. Unlike Table 3's CRUD verb heuristics, ops methods have free verbs and free return types, so they take a fixed action-style shape (Step 5o). An aggregate with zero ops diagrams produces no Table 3o rows and behaves exactly as before this capability existed.
Arguments
<domain_diagram>— path to the Mermaid domain class diagram (<dir>/<stem>.md). Sibling diagrams and the output spec file are derived from this path.
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.
- 12d ago First seen · 320 lines · 55 tokens per session scan A 79aa922f6b90
endpoint-tables-writer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 55 tokens to every session and 9,881 once invoked, about $0.0002 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-10-04.
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…