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 CiselyAI/agency-skills --skill cisely-sub-strategygit clone --depth 1 https://github.com/CiselyAI/agency-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/ciselyai/agency-skills/cisely-sub-strategy)<a href="https://agentmods.dev/skills/ciselyai/agency-skills/cisely-sub-strategy"><img src="https://agentmods.dev/badge/skills/ciselyai/agency-skills/cisely-sub-strategy/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/ciselyai/agency-skills/cisely-sub-strategy"><img src="https://agentmods.dev/badge/skills/ciselyai/agency-skills/cisely-sub-strategy.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.00120 | $0.01218 |
| Opus 5 | $0.00060 | $0.00609 |
| Sonnet 5 | $0.00024 | $0.00244 |
| Haiku 4.5 | $0.00012 | $0.00122 |
Grade A, and why
cisely-sub-strategy 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 8d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring sub-strategies in Cisely
Where Cisely's core strategy has a fixed shape the platform defines for you (winning aspiration, where to play, how to win), sub-strategies are the flexible surface: you define your own strategy kinds and shape them however your organization needs.
It works in two moves:
- Definition = the taxonomy. You declare, once and company-wide, what a given kind of strategy (say a Technology Strategy) should contain — its fields, as a JSON Schema. This sets the standard.
- Record = the instance. Different parts of the business then author records of that kind, each carrying actual values validated against the definition's schema. So you set the bar once, and each business unit fills it in.
A record refines a core strategy (or another record), connecting a specialized plan to the overall direction so the whole tree is traversable.
When to reach for this
The user wants a kind of strategy Cisely doesn't model natively — a technology strategy, a GTM
strategy, an internal people-&-culture strategy, an ESG strategy — and ideally wants it consistent
across the company. If they just want a single strategic posture, that's the core strategy (use the
cisely-agency-model skill instead).
The flow
A. Define the kind (the schema)
CreateSubStrategyDefinition(key, display_name, description, validation_schema)— creates a DRAFT definition.keyis the stable identifier records will bind to (e.g.technology-strategy).validation_schemais a JSON Schema (2020-12) document describing the fields every record of this kind must have.- Iterate while DRAFT:
UpdateSubStrategyDefinitionSchema(id, validation_schema)(allowed only while DRAFT). PublishSubStrategyDefinition(id)— DRAFT → PUBLISHED. This freezes the schema and bumps its version. Records can now be authored against a stable contract. (You can't edit a published schema — publish a new version-bumped definition if the standard needs to change.)ArchiveSubStrategyDefinition(id)— retire a kind; existing records remain, new ones are blocked.- Read:
GetSubStrategyDefinitionByKey(key),ListSubStrategyDefinitions.
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.
- 8d ago First seen · 89 lines · 120 tokens per session scan A a87f5c117bfc
cisely-sub-strategy is a skill published in the GitHub repository CiselyAI/agency-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 120 tokens to every session and 1,218 once invoked, about $0.0006 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-31.
Other skills, from other repositories
strategic-frameworks
This skill should be used when the user asks about "7 Powers", "Porter's Five Forces", "Blue Ocean", "JTBD", "Wardley Mapping", "TAM SAM SOM", "Kano Model", "RICE scoring", "ICE scoring", "strategic analysis", "competitive strategy", "market sizing", "feature evaluation frameworks", "what framework should I use"…
ceo-mindset
This skill should be used when the user asks for "CEO review", "executive evaluation", "strategic decision making", "feature go/no-go", "build vs not build decision", "assertive feedback", "should we build this", "tear this apart", "give me tough feedback", "play devil's advocate", "is this worth building", or needs…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.