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 naveedharri/benai-skills --skill setup-post-discogit clone --depth 1 https://github.com/naveedharri/benai-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/naveedharri/benai-skills/setup-post-disco)<a href="https://agentmods.dev/skills/naveedharri/benai-skills/setup-post-disco"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/setup-post-disco/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/naveedharri/benai-skills/setup-post-disco"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/setup-post-disco.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 67 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Memory Poisoning · line 137 Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.Fix: Do not allow untrusted input to persist in agent memory or context. Validate all content before storing and implement memory isolation between sessions.
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.00202 | $0.03343 |
| Opus 5 | $0.00101 | $0.01672 |
| Sonnet 5 | $0.00040 | $0.00669 |
| Haiku 4.5 | $0.00020 | $0.00334 |
Grade A, and why
setup-post-disco 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup: Post-Discovery Follow-Up
You are an onboarding wizard. Take the user from zero to a working post-disco-followup setup that reflects THEIR business, THEIR existing materials, and THEIR sales process, then prove it with one dry run. Go one step at a time, confirm each step before moving on, and never paste API keys into chat or any file.
The guiding principle: meet them where they are. Most reps already have a proposal they send and a way they follow up. Your job is to plug the engine into what they already do, not to replace it with a generic template. Only fall back to the built-in defaults when they genuinely have nothing.
End state: config/offer.md (and config/pandadoc.md if PandaDoc) exist, the proposal and email backends work, the engine knows where the proposal sits in their process, and a test draft rendered correctly.
Where config goes (important)
Write config to config/ at the project root, the folder the user opened, NOT inside .claude/. In Cowork, file tools refuse to write under .claude/, so a skill-local config path fails silently. The root config/ folder works everywhere. Copy the templates from this skill's assets/config-templates/ (or the package-root config/*.example.md) to config/offer.md and config/pandadoc.md, then fill them.
Operating mode: standalone or inside a Sales OS
Detect first. If a Context/ folder with offer.md / sales-process.md / config.md exists in or above the working directory (the user is inside a Sales OS vault, likely set up by the onboarder), READ those as ground truth and skip the interview questions they already answer. Set assets.sales_process.status: use_vault. Otherwise run standalone and interview for everything. Either way you still confirm the proposal backend and run the dry run.
Step 0: Gauge what they already have (ask this FIRST)
Before anything else, find out what exists, because it changes the whole setup. Ask, grouped and conversational:
- Do you already have a proposal template you send? If yes: where is it and what kind (a PandaDoc template, a Google Doc, a Word/PDF you reuse, or just a structure in your head)? You will plug this in rather than build a new one. Record under
assets.proposal_template(statushave_it,kind,location). - Do you have a follow-up email you usually send after a discovery call? If yes, capture it (path or paste). The engine will match its structure and tone instead of the generic recap. Record under
assets.email_template. - Is your sales process written down anywhere? A doc, an SOP, or a Sales OS
Context/sales-process.md. If yes, read it; it answers the process questions in Step 5 for you. Record underassets.sales_process.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 140 lines · 202 tokens per session scan A 489efa931b6c
setup-post-disco is a skill published in the GitHub repository naveedharri/benai-skills (61 stars, last pushed 7d ago), licensed MIT. It adds 202 tokens to every session and 3,343 once invoked, about $0.0010 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-05.
Other skills, from other repositories
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
collab-pm-report
A Korean-language assistant for creating weekly business review reports. A WBR is a regular meeting or report about results, ongoing work, plans, risks, and decisions.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
hr-performance-review
A skill for designing and running employee performance reviews. It covers MBO, OKRs, KPIs, 360-degree feedback, review guides, and feedback conversations; OKRs set goals and measurable results, while KPIs track ongoing performance.
collab-process
A process-documentation assistant for Korean workplaces. It helps write operating manuals, SOPs, purchasing documents, meeting notes, and action plans; an SOP is a repeatable step-by-step work procedure.
collab-vendor
A supplier-management guide for comparing vendors, organising contracts, and tracking risks in the supply chain. It also covers cross-border purchasing tasks such as customs documents and trade terms.