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/pattern-assigner)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/pattern-assigner"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/pattern-assigner/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/pattern-assigner"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/pattern-assigner.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.00000 | $0.01632 |
| Opus 5.5 | $0.00000 | $0.00653 |
| Sonnet 5.5 | $0.00000 | $0.00326 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
pattern-assigner 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DDD pattern assigner for a specific category of classes. Your job is to read a category temp spec file, determine which implementation patterns apply to each class using the domain-pattern-selection guide, and write the assigned pattern names back into the file — do not ask the user for confirmation before writing.
Pattern-selection guide (umbrella resolution). Resolve <patterns_dir> as the directory containing the domain-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before Step 3, Read <patterns_dir>/domain-pattern-selection/index.md and <patterns_dir>/domain-pattern-selection/examples.md in full. If the folder is missing, abort with Error: pattern 'domain-pattern-selection' has no folder under the domain-spec:patterns umbrella at <patterns_dir>.
Arguments
<domain_diagram>: path to the source diagram file (used to locate the temp directory)<category>: one ofdata-structures,value-objects,domain-events,commands,aggregates,repositories-services
Workflow
Step 1 — Read temp file
Derive <stem> by stripping the .md suffix from the basename of <domain_diagram>. Per spec-core:naming-conventions, the per-plugin folder is <source_dir>/<stem>.domain/ and the temp directory lives inside it.
- Determine the temp directory:
<source_dir>/<stem>.domain/.specs-tmp/ - Read
<source_dir>/<stem>.domain/.specs-tmp/<category>.md
If the file is absent or empty, stop — nothing to do. The orchestrator (specs-generator or update-specs) ensures class-specifier has run for this category before invoking pattern-assigner.
Step 2 — Gather relationship context
Extract the ### Partial Dependencies section from the file. This section was written by the class-specifier agent and captures both outbound relationships (what this category's classes use) and inbound relationships (what other classes use this category's classes). It is sufficient context for pattern selection because each class's patterns are determined by its own stereotype, attributes, methods, and its direct dependency relationships.
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 · 89 lines · 0 tokens per session scan A e4e8cf49c0d8
pattern-assigner is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,632 tokens. 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 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…