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 agentmods add skills/abilityai/trinity/dd-sourcingnpx skills add Abilityai/trinity --skill dd-sourcinggit clone --depth 1 https://github.com/Abilityai/trinityWhat 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 | $0.00029 | $0.00648 |
| Opus 5 | $0.00015 | $0.00324 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
dd-sourcing 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Documentation Standards
All due diligence findings must be traceable to their sources. This enables audit trails, follow-up verification, and legal defensibility.
Source Quality Tiers
Tier 1: Primary Sources (Highest Credibility)
- SEC filings (10-K, 10-Q, S-1)
- Court documents and legal filings
- Government databases (USPTO, state registrations)
- Company's own audited financials
- Direct customer/reference interviews
Tier 2: Secondary Sources (High Credibility)
- Established data providers (Crunchbase, PitchBook, CB Insights)
- Major news outlets (WSJ, Bloomberg, TechCrunch)
- Industry analyst reports (Gartner, Forrester)
- LinkedIn profiles (for employment verification)
- Academic research and papers
Tier 3: Tertiary Sources (Use with Caution)
- Social media posts
- Blog articles
- Glassdoor reviews
- Wikipedia (only as starting point)
- Forum discussions
Citation Format
Every fact must include a source citation:
{
"source": {
"name": "Full source name",
"type": "SEC_FILING | NEWS | DATA_PROVIDER | INTERVIEW | GOVERNMENT | OTHER",
"url": "https://... (if available)",
"access_date": "2024-01-15",
"publication_date": "2024-01-10",
"tier": 1,
"excerpt": "Relevant quote or data point"
}
}
Best Practices
DO:
- Capture URLs at time of access (pages change/disappear)
- Note the access date for all web sources
- Quote relevant passages, don't just link
- Use multiple sources for critical claims
- Prefer recent sources over older ones
DON'T:
- Cite a source you haven't actually reviewed
- Use company press releases as independent verification
- Rely on a single source for material claims
- Cite sources behind paywalls without noting limitation
- Mix up "stated by company" vs "independently verified"
Source Tracking in Output
Include a sources section in every analysis:
{
"sources_used": [
{
"id": "S1",
"name": "Crunchbase - Acme Corp Profile",
"url": "https://crunchbase.com/...",
"access_date": "2024-01-15",
"tier": 2,
"used_for": ["funding_history", "employee_count"]
}
],
"source_statistics": {
"tier_1": 3,
"tier_2": 8,
"tier_3": 2,
"total": 13
}
}
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.
- 2d ago First seen · 99 lines · 29 tokens per session scan A f033a751adb6
dd-sourcing is a skill published in the GitHub repository Abilityai/trinity (496 stars, last pushed 4d ago), licensed Apache-2.0. It adds 29 tokens to every session and 648 once invoked, about $0.0001 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
audit-support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
advogado-especialista
Advogado especialista em todas as areas do Direito brasileiro: familia, criminal, trabalhista, tributario, consumidor, imobiliario, empresarial, civil e constitucional.
kyc-doc-parse
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
kyc-rules
Apply the firm's KYC/AML rules grid to a parsed onboarding record — assign a risk rating, list every rule outcome with the rule cited, and flag what's missing or escalation-worthy. Use after kyc-doc-parse; this skill decides nothing, it scores and routes.
analytical-method-validation
Plan, execute, and document validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP / / , ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays…
prior-auth-packet-builder
Build a concise prior authorization packet from local case files and payer policy docs.