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 tough-tongue/demo-prep-skills --skill setup-companygit clone --depth 1 https://github.com/tough-tongue/demo-prep-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/tough-tongue/demo-prep-skills/setup-company)<a href="https://agentmods.dev/skills/tough-tongue/demo-prep-skills/setup-company"><img src="https://agentmods.dev/badge/skills/tough-tongue/demo-prep-skills/setup-company/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/tough-tongue/demo-prep-skills/setup-company"><img src="https://agentmods.dev/badge/skills/tough-tongue/demo-prep-skills/setup-company.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.00051 | $0.01310 |
| Opus 5 | $0.00026 | $0.00655 |
| Sonnet 5 | $0.00010 | $0.00262 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
setup-company 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Company Profile Setup
Create a company-profile.md file that all other demo-prep skills use as context. Run this once when you first install the skills, and update it whenever your product, positioning, or team changes.
When to Use
- First time setting up demo-prep-skills
- User says "set up my demo prep profile" or "configure my company"
- The
company-profile.mdfile doesn't exist yet - User wants to update their company info or positioning
Process
Step 1: Check for Existing Profile
Look for company-profile.md in the workspace root. If it exists, ask: "You already have a company profile. Want to update it or start fresh?"
Step 2: Gather Information
Ask the user for each section below. Ask questions conversationally — don't dump a form. If they provide a website URL or docs link, research it first and pre-fill what you can, then confirm with the user.
Required:
- Company name and website
- What you sell — 2-3 sentence description. What problem does it solve? Who is it for?
- Your name and role — Name, title, LinkedIn URL (optional)
- Your ICP — Ideal customer profile: role titles, company size, industries you sell to
- Key differentiators — 2-3 things that make you different from alternatives
- Common objections — Top 3 objections prospects raise, and how you typically respond
Optional (but improves output quality):
- Docs URL — An
llm.txtfile, docs site, or knowledge base the agent can reference for deeper product knowledge - Pricing — Pricing model and ranges (this stays local, never shared)
- Proof points — Customer logos, case study headlines, key metrics (e.g., "200+ customers", "30% conversion lift")
- Your background — Education and previous companies (used to find shared connections with prospects)
- Co-founders / key team — Names and backgrounds (for additional shared-connection matching)
- Sales motion — How you sell: inbound-led, outbound, PLG, enterprise, channel
- Competitor list — Top 3-5 competitors and your positioning against each
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 · 132 lines · 51 tokens per session scan A 9ca4d4b47688
setup-company is a skill published in the GitHub repository tough-tongue/demo-prep-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,310 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…