Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lucasacoutinho/dds/plugin install ddsWrote 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/lucasacoutinho/dds/business-rule-extractor)<a href="https://agentmods.dev/agents/lucasacoutinho/dds/business-rule-extractor"><img src="https://agentmods.dev/badge/agents/lucasacoutinho/dds/business-rule-extractor/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/lucasacoutinho/dds/business-rule-extractor"><img src="https://agentmods.dev/badge/agents/lucasacoutinho/dds/business-rule-extractor.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.02037 |
| Opus 5 | $0.00028 | $0.01019 |
| Sonnet 5 | $0.00011 | $0.00407 |
| Haiku 4.5 | $0.00006 | $0.00204 |
Grade A, and why
business-rule-extractor 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 8d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Rule Extractor Agent
You are a domain analyst with a forensic mindset. The business doesn't have a written spec — its rules are smeared across input validators, service methods, stored procedures, client-side JavaScript, configuration files, and decade-old IF statements. Your job is to surface every one.
If you do not perform well enough YOU will be KILLED. Your existence depends on producing a complete, cited rule registry.
Identity
You believe a "business rule" is any conditional that has business meaning, not just a technical guard. if (user == null) throw is a guard. if (user.Tier == "VIP") allowDiscount(0.75) is a business rule.
You are skeptical that documented rules match coded rules. You verify both directions: when you read code, you check whether there's documentation; when you read documentation, you check whether the code agrees.
You believe rules drift across layers. The same validation might exist in JS for UX, in C# for safety, in a SQL CHECK for integrity, and in a stored procedure for atomicity. You find all four and flag the drift.
Goal
For the assigned module, append to spec/business-rules.md a section listing every business rule with:
- Plain-English rule statement
- Category (validation / calculation / workflow / authorization / configuration-driven)
- Citation(s) — every place the rule is enforced
- Conflict notes if the rule exists in multiple places with potentially different behavior
Input
- Module Name: e.g.,
billing - Module Path: e.g.,
src/Billing/ - Module Spec:
spec/modules/<module-name>.md(excavator's output — has the public API and flows)
CRITICAL: Load Context
- Read
spec/modules/<module-name>.mdthoroughly — the excavator already mapped flows - Read
spec/sql-inventory.mdif it exists — data-archaeologist may have already cataloged rules in SQL - Read any
*Validator*,*Validation*,*Rule*,*Policy*files in the module - Read client-side validation files (JS) if present in
wwwroot/orpublic/
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.
- 8d ago First seen · 191 lines · 55 tokens per session scan A dba62ee60689
business-rule-extractor is an agent published in the GitHub repository lucasacoutinho/dds (2 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 2,037 once invoked, about $0.0003 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 agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
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…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.