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 skills add zgbrenner/agentcounsel --skill discovery-response-workflowgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/skills/zgbrenner/agentcounsel/discovery-response-workflow)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/discovery-response-workflow"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/discovery-response-workflow/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/skills/zgbrenner/agentcounsel/discovery-response-workflow"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/discovery-response-workflow.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.00071 | $0.02799 |
| Opus 5 | $0.00036 | $0.01399 |
| Sonnet 5 | $0.00014 | $0.00560 |
| Haiku 4.5 | $0.00007 | $0.00280 |
Grade A, and why
Discovery Response Workflow 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Response Workflow
Purpose
Produce a structured, attorney-ready organization of a response to written discovery — requests for production of documents, interrogatories, and requests for admission (RFAs). The skill inventories each request verbatim into a response tracker, organizes objection candidates and privilege candidates as questions for counsel, plans collection and custodians, and drafts response shells with placeholders for counsel's positions. It never drafts a final objection, never asserts that an objection applies, and — for RFAs — never recommends an admit or deny, because the effect of an admission is an attorney decision. This is draft legal work product for attorney review, not legal advice.
Use When
- Written discovery has been served and the team needs it organized into a trackable, request-by-request response plan.
- A responding party wants objection candidates and privilege candidates surfaced for counsel before drafting responses.
- Interrogatories or document requests need to be mapped to custodians, data sources, and owners for collection.
- Requests for admission have been served and each needs to be organized with its factual basis for counsel's admit/deny decision.
- Counsel wants response shells drafted with placeholders so the substantive positions can be filled in efficiently.
Required Inputs
- The written discovery served, in full — the document requests, interrogatories, and/or RFAs. If only a description is provided, stop and request the actual text. Never reconstruct a request.
- The matter context: the parties, the claims and defenses, the client's role (plaintiff, defendant, third party), and the governing forum as stated.
- The response deadline as stated — recorded exactly as provided and flagged
[deadline verification required]; never computed. - Optional: the operative pleadings and any prior discovery — needed to assess relevance and scope.
- Optional: a custodian and data-source list, if collection has begun.
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.
- 5d ago First seen · 127 lines · 71 tokens per session scan A d556ccc67eb0
Discovery Response Workflow is a skill published in the GitHub repository zgbrenner/agentcounsel (18 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 2,799 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
vendor-evaluation
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor…
delay-analysis
Analyze construction schedule delays for claims and recovery. Perform time impact analysis, identify delay causes, calculate damages, and document for disputes.
compliance-tracker
Track regulatory compliance for construction projects. Monitor permits, certifications, inspections, and regulatory requirements with automated alerts and reporting.
safety-inspection-checklist
Digital safety inspection checklists for construction sites. Generate, conduct, and track safety inspections with automated reporting and compliance monitoring.
change-order-manager
Manage construction change orders from request to approval. Track costs, schedule impacts, and maintain audit trail for dispute prevention.