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 Stallin-Sanamandra/b2b-saas-marketing-skills --skill account-research-brief-generatorgit clone --depth 1 https://github.com/Stallin-Sanamandra/b2b-saas-marketing-skillsWrote 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/stallin-sanamandra/b2b-saas-marketing-skills/account-research-brief-generator)<a href="https://agentmods.dev/skills/stallin-sanamandra/b2b-saas-marketing-skills/account-research-brief-generator"><img src="https://agentmods.dev/badge/skills/stallin-sanamandra/b2b-saas-marketing-skills/account-research-brief-generator/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/stallin-sanamandra/b2b-saas-marketing-skills/account-research-brief-generator"><img src="https://agentmods.dev/badge/skills/stallin-sanamandra/b2b-saas-marketing-skills/account-research-brief-generator.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.00122 | $0.05934 |
| Opus 5 | $0.00061 | $0.02967 |
| Sonnet 5 | $0.00024 | $0.01187 |
| Haiku 4.5 | $0.00012 | $0.00593 |
Grade A, and why
account-research-brief-generator 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Account Research Brief Generator
A repeatable framework for turning a company name into a BDR-ready research brief in 10-60 minutes depending on tier. Reduces inconsistent manual research by giving BDRs a tier-calibrated workflow that produces a standardized brief across researchers, accounts, and outreach waves.
Why This Skill Exists
Most account research is wasted work. BDRs spend an hour on a single account, find three usable insights, and the rest of the data dies in a Notion doc no one reads. By the time outreach starts, half the intel is stale and none of it ties to a specific message angle.
This skill fixes three failure modes:
-
Inconsistent depth across accounts. Tier-1 accounts get 90 minutes of research; tier-2 accounts get 10. The brief format here scales depth to tier without losing structure.
-
Research that doesn't drive outreach. Generic "they raised a Series B" notes don't tell a BDR what to say. Every section in this brief ends with a "so what" — the implication for messaging.
-
No reusable artifact. Each researcher works from scratch. This skill produces a standardized brief that can be reviewed, refined, and reused across multiple outreach waves.
When to Use This Skill
- Preparing outreach for a specific named account (single brief)
- Building research packets for a tier-1 ABM cohort (batch briefs)
- Onboarding a new BDR with their first account list
- Refreshing intel on accounts re-entering active outreach after 60+ days
- Pre-call research for sales discovery on a recycled pipeline account
- Building "account snapshots" for executive sponsor outreach
- Validating that an account on the target list actually fits the ICP after research
When NOT to Use This Skill
- Building the target account list itself (use
abm-program-orchestratorfor list construction) - Writing the outreach sequences (use
bdr-enablement-generatorafter research is done) - Mass-research on 1000+ accounts (this is a depth tool, not a breadth tool — use intent data platforms for breadth)
- Customer research for expansion (different motion; expansion needs usage data, not external signals)
- Competitive battlecards (use
competitive-battlecard-generator)
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 · 537 lines · 122 tokens per session scan A 76e4b70a9a52
account-research-brief-generator is a skill published in the GitHub repository Stallin-Sanamandra/b2b-saas-marketing-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 122 tokens to every session and 5,934 once invoked, about $0.0006 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 skills, from other repositories
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…
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
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…
nist-800-53
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200 system categorization, control tailoring and overlays, privacy controls (PT family), supply chain risk management (SR…
hipaa-compliance
Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any…
GRC & Compliance
Governance, risk, and compliance — risk assessment and scoring, control mapping across NIST CSF 2.0 / ISO 27001:2022 / SOC 2 / CIS Controls v8, gap analysis, audit evidence preparation, and security policy generation.