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 bankruptcy-diligence-request-listgit 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/bankruptcy-diligence-request-list)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/bankruptcy-diligence-request-list"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/bankruptcy-diligence-request-list/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/bankruptcy-diligence-request-list"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/bankruptcy-diligence-request-list.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.00030 | $0.01376 |
| Opus 5 | $0.00015 | $0.00688 |
| Sonnet 5 | $0.00006 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
Bankruptcy Diligence Request List 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bankruptcy Diligence Request List
Purpose
Generate a bankruptcy or distressed-transaction diligence request list, organized by workstream with priority, rationale, owner, and follow-up, so attorney-supervised diligence can request, track, and escalate the right documents. This skill scopes and organizes diligence requests; it determines no legal exposure and no claim value. It produces draft legal work product for attorney review — not legal advice.
Use When
- A distressed M&A deal, a bankruptcy asset sale, creditor or lender diligence, a restructuring transaction, or a plan negotiation needs a diligence request list.
- A diligence team needs requests organized by workstream with priority, rationale, and ownership.
- Diligence follow-ups must be tracked against documents produced.
Required Inputs
- The transaction or matter type and stage.
- Debtor profile, the user's party role (buyer, lender, creditor, committee, debtor, or other), and case status if known.
- Court or jurisdiction if known, or
[verify jurisdiction]. - The workstreams in scope — for example debtor organization, debt structure, liens and collateral, contracts, litigation, claims, taxes, employees and benefits, environmental if relevant, real estate, intellectual property, financials, cash management, insider transactions, avoidance actions, regulatory issues, and sale or plan documents if relevant.
- Documents already provided, with source references.
- Known debt, lien, contract, litigation, or claim facts the user reports.
If the transaction/matter type, the user's role, or the workstreams in scope
are missing, record them as not provided and return the missing-information
list first.
Do Not Use When
- The request is to determine legal exposure, claim value, or lien priority.
- The request is to conclude on avoidance-action risk or any legal question.
- The request is for legal advice or a deadline calculation.
Also out of scope (this skill does not): determine legal exposure, claim value, lien validity or priority, or avoidance-action risk; conclude on any legal question; or constitute legal advice.
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 · 135 lines · 30 tokens per session scan A af10fbf1b5f5
Bankruptcy Diligence Request List is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,376 once invoked, about $0.0002 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-30.
Other skills, from other repositories
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.