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 anotb/management-consulting-plugin --skill engagement-setupgit clone --depth 1 https://github.com/anotb/management-consulting-pluginWrote 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/anotb/management-consulting-plugin/engagement-setup)<a href="https://agentmods.dev/skills/anotb/management-consulting-plugin/engagement-setup"><img src="https://agentmods.dev/badge/skills/anotb/management-consulting-plugin/engagement-setup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00746 |
| Opus 5 | $0.00022 | $0.00373 |
| Sonnet 5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
engagement-setup 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 today.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Setup
Turn the agreed engagement into a shared problem definition, access to evidence, working ownership, and useful early progress. Preserve the contract, approved scope, existing work, and client's operating requirements. Do not replay sales qualification after award or impose enterprise governance on a small advisory task.
Use the brief, contract, known team, timeline, and available data. Draft supported portions while recording missing information. Ask only when a missing answer changes the scope or makes the plan unusable. Mark unknown stakeholder positions and proposed commitments rather than filling them with plausible names, dates, or attitudes.
Prepare the launch
Identify the outcome, decision-maker, scope boundaries, deliverables, success evidence, dependencies, and near-term decisions. Compare expectations with the agreement and make discrepancies visible. Separate contractual commitments from planning assumptions.
Map affected groups and decision roles. Use a power-interest matrix when it helps: high power/high interest = manage closely; high power/low interest = keep satisfied; low power/high interest = keep informed and hear their input; low power/low interest = monitor proportionately. Influence and interest do not establish support or opposition. Record stance from evidence and revisit it when information changes.
Design the kickoff around unresolved alignment and decisions. Move routine information into a proportionate pre-read if time permits. Select a duration and participants to fit the brief; a kickoff can be a short working session rather than a workshop. Identify the authority or representation required for decisions without treating absence as automatic evidence of disengagement.
For a charter, use project charter template. Adapt fields to the engagement; do not require every field to be finalized live or describe a charter as replacing the contract.
Design discovery
Tie each question to the decision it will inform. Choose data review, interviews, observation, working sessions, or a survey according to the evidence needed. Use discovery methods for requests, interviews, and synthesis.
What ships with it
2 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.
- today Changed · -383 lines · -45 tokens per session 9cdf50884740
- 8d ago First seen · 427 lines · 88 tokens per session scan A 772738fb4083
engagement-setup is a skill published in the GitHub repository anotb/management-consulting-plugin (49 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 746 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-08-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.