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 tomzx/agents --skill enable-teamsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/enable-teams)<a href="https://agentmods.dev/skills/tomzx/agents/enable-teams"><img src="https://agentmods.dev/badge/skills/tomzx/agents/enable-teams/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/tomzx/agents/enable-teams"><img src="https://agentmods.dev/badge/skills/tomzx/agents/enable-teams.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.00038 | $0.00425 |
| Opus 5 | $0.00019 | $0.00212 |
| Sonnet 5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
enable-teams 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 6d 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
Enable Teams
A launch fails in the field when sales, support, and customer success cannot explain or defend the product. This skill produces the enablement kit: the artifacts each front-line team needs to do their job without escalating to the PM.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. prd.md,messaging.md, andlaunch-plan.md.
Steps
- Identify the teams to enable: sales, support, customer success, and any internal users.
- For each team, produce the artifacts they need:
- Sales: target customer profile, discovery questions, objection-handling, pricing/packaging summary, competitive talking points.
- Support: what it does, known limitations, how to troubleshoot common issues, escalation path.
- Customer success: migration/transition guidance for existing customers.
- Run a dry-run or review with a representative from each team; capture what they could not answer.
- Fill the gaps until a front-line team member can handle the common cases unaided.
- Write
enablement-kit.mdto the initiative directory (it can reference separate asset files).
Output Format
Use the template at skills/pdlc/templates/initiatives/enablement-kit.md.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- Each front-line team has role-specific artifacts
- Objection-handling and troubleshooting cover the common cases
- A representative from each team reviewed it (or a gap is flagged)
- Escalation path defined
Next Step
Load set-pricing if not done, then run the Launch gate via make-decision.
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.
- 6d ago First seen · 45 lines · 38 tokens per session scan A 522820c5d414
enable-teams is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 425 once invoked, about $0.0002 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-03.
Other skills, from other repositories
gsd-milestone-summary
Generate a comprehensive project summary from milestone artifacts for team onboarding and review.
git-pr-workflows-onboard
You are an expert onboarding specialist and knowledge transfer architect with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You.
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
interview-system-designer
Design hiring interviews, competency matrices, question banks, scoring rubrics, and interviewer calibration for a specified role.
product-adoption
Diagnose and design product adoption for onboarding, activation, behavior change, feature discovery, rollout, and sustained use after launch. Covers consumer, B2B, internal-tool, and public-service contexts with evidence-based decision points and cohort segmentation. Does not own acquisition campaigns or marketing…
sales-coaching
Sales coaching system — REKS diagnosis (Jacco van der Kooij / Winning by Design), MEDDICC deal reviews (Andy Whyte), JOLT for indecision, call coaching (Jon Barrows, Jason Bay), manager cadence (Kevin Dorsey), and founder-as-coach. Use when building coaching programs, 1:1s, deal reviews, call feedback, or improving…