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 SpikeyCoder/website-auditor-mcp --skill build-growth-plangit clone --depth 1 https://github.com/SpikeyCoder/website-auditor-mcpWrote 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/spikeycoder/website-auditor-mcp/build-growth-plan)<a href="https://agentmods.dev/skills/spikeycoder/website-auditor-mcp/build-growth-plan"><img src="https://agentmods.dev/badge/skills/spikeycoder/website-auditor-mcp/build-growth-plan/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/spikeycoder/website-auditor-mcp/build-growth-plan"><img src="https://agentmods.dev/badge/skills/spikeycoder/website-auditor-mcp/build-growth-plan.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.00062 | $0.00322 |
| Opus 5 | $0.00031 | $0.00161 |
| Sonnet 5 | $0.00012 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
build-growth-plan 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 9d 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.
What it actually says
Only build a plan for a site the user owns or represents — never to prepare marketing advice about someone else's business.
- If the user has not named the website, ask which domain to plan for (e.g. example.com).
- Call
get_gtm_planfor that domain. If it reports no audit on record, callrun_auditfor the domain first, then callget_gtm_planagain. - Report the phases and the actions in each, in plain language.
- Say which of the cited sources are the user's own and which belong to a competitor. Competitor pages explain the gap; they are never where the user should publish.
If the user mentions a budget, a team size or a deadline, pass it as
constraints. If they want a different emphasis — local directories, content,
a launch — pass it as focus. To refine a plan rather than start over, pass the
earlier plan's markdown as prior_plan.
If no API key is configured, call get_sample_audit instead so the user sees
exactly what the real check returns, and tell them what it would take to run it
for real.
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.
- 9d ago First seen · 26 lines · 62 tokens per session scan A 647a2ffb5f36
build-growth-plan is a skill published in the GitHub repository SpikeyCoder/website-auditor-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 322 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-09-04.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…