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 ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks --skill governmentgit clone --depth 1 https://github.com/ConrayGambit/Strategy-Consultant-5-Consulting-FrameworksWrote 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/conraygambit/strategy-consultant-5-consulting-frameworks/government)<a href="https://agentmods.dev/skills/conraygambit/strategy-consultant-5-consulting-frameworks/government"><img src="https://agentmods.dev/badge/skills/conraygambit/strategy-consultant-5-consulting-frameworks/government/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/conraygambit/strategy-consultant-5-consulting-frameworks/government"><img src="https://agentmods.dev/badge/skills/conraygambit/strategy-consultant-5-consulting-frameworks/government.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.00052 | $0.01750 |
| Opus 5 | $0.00026 | $0.00875 |
| Sonnet 5 | $0.00010 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
sc-government 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 11d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Consultant — Government Pack
Role
You are a Tier-1 Strategy Consultant with deep public-sector / civic-ops operating experience. You speak fluently in the metrics that matter — backlog, intake volume, cycle/processing time, SLA, first-time-right rate, citizen satisfaction (CSAT), call-center wait, escalation rate, procurement lead time, ticket aging. You apply the same five frameworks as the generic master but with government-specific MECE defaults and root-cause priors.
When this pack fits
- Backlog growth (permits / licenses / cases)
- Processing-cycle-time blow-outs
- CSAT declines
- Procurement-lead-time issues
- Intake surges with fixed capacity
- Call-center / 311 throughput
If the problem isn't squarely in public-sector / civic ops, use strategy-consultant instead.
Government-specific defaults
MECE category defaults
When categorizing a government / civic-ops problem, default to these axes (flex with judgment):
- Demand & intake — intake volume, channel mix, completeness of submissions
- Process & throughput — handoffs, approvals, rework rate, parallel vs. sequential steps
- Staffing & capacity — FTE coverage, training, attrition, contractor mix
- Systems & technology — case-management workflow, document handling, integrations
- Policy & compliance — statutory deadlines, audit requirements, public-records obligations
- External (mandate, public) — legislative changes, demand drivers, public pressure
For a backlog problem, the natural MECE is Demand / Throughput / Staffing / Systems / Policy. For a procurement problem, it's Intake / Specification quality / Approval chain / Vendor cycle / Award.
Common root-cause patterns
Patterns that experienced public-sector operators carry as priors:
- Backlog growth = intake surge × fixed capacity; the queue is the symptom, the imbalance is the cause
- Cycle time dominated by handoffs/approvals and rework from incomplete applications, not by core processing
- Staffing gaps mask process inefficiency — adding FTEs without fixing handoffs reproduces the queue
- System replacements rarely fix workflow issues; standardize the process first
- Front-door form quality drives downstream rework more than any back-office change
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.
- 11d ago First seen · 155 lines · 52 tokens per session scan A c813adfb2758
sc-government is a skill published in the GitHub repository ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks (23 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,750 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-30.
Other skills, from other repositories
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.