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 modest-curator478/claude-skills --skill hubspot-auditgit clone --depth 1 https://github.com/modest-curator478/claude-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/modest-curator478/claude-skills/hubspot-audit)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/hubspot-audit"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/hubspot-audit/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/modest-curator478/claude-skills/hubspot-audit"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/hubspot-audit.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.00154 | $0.02062 |
| Opus 5 | $0.00077 | $0.01031 |
| Sonnet 5 | $0.00031 | $0.00412 |
| Haiku 4.5 | $0.00015 | $0.00206 |
Grade A, and why
hubspot-audit 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.
This is a copy
100% identical to hubspot-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HubSpot Instance Audit: Structural Health Review
This skill runs when the user needs to audit an existing HubSpot instance. It produces a structured audit framework across six domains, identifies the highest-impact problems first, and delivers a prioritized remediation plan.
HOW TO SET UP THIS SKILL
This skill works best when the user provides context about their instance. Ask for the following if not already provided:
- How long the instance has been active
- Rough number of contacts, companies, and open deals
- Whether they inherited it or built it
- What Sales and Marketing teams are using it for
- Any known pain points
If no context is provided, run the audit framework as a diagnostic checklist the user can work through manually.
The Six Audit Domains
Run through each domain. For each, identify what to look for, what the red flags are, and what good looks like.
Domain 1: Deal pipeline and stage design
What to look for:
- How many deal stages exist and whether they reflect how sales actually works, not how someone wished it worked
- Whether stage names are action-oriented (what happens at this stage) or status-oriented (where the deal sits)
- Whether there is a clear exit criteria for each stage
- Whether deals are piling up in one or two stages, which signals a stage definition problem, not a sales problem
- Whether the pipeline has stages that no one uses
Red flags:
- More than 8 stages in a single pipeline
- Stage names like "In Progress" or "Active" with no definition
- A large percentage of deals stuck in the same stage for more than 30 days
- Multiple pipelines that are nearly identical
- No close date discipline (all deals show the same default date)
What good looks like: Each stage has a name that describes what sales did to get there, a clear next action, and an exit criteria that both sales and marketing agree on. Deal velocity is visible and not artificially inflated.
Domain 2: Workflow and automation health
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 · 270 lines · 154 tokens per session scan A fe1cb53faa64
hubspot-audit is a skill published in the GitHub repository modest-curator478/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 154 tokens to every session and 2,062 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hubspot-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
nextdns-cli
NextDNS CLI client best practices for installation, configuration, and management of DNS-over-HTTPS proxy. This skill should be used when installing NextDNS on routers, servers, or client devices, configuring DNS settings, managing the daemon, or troubleshooting DNS issues. Triggers on tasks involving NextDNS CLI…