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 agentmods add rules/ciselyai/agency-skills/cisely-agency-modelgit 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/rules/ciselyai/agency-skills/cisely-agency-model)<a href="https://agentmods.dev/rules/ciselyai/agency-skills/cisely-agency-model"><img src="https://agentmods.dev/badge/rules/ciselyai/agency-skills/cisely-agency-model.svg" alt="Measured on agentmods" 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.00045 | $0.00355 |
| Opus 5 | $0.00023 | $0.00178 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
cisely-agency-model 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
When the user asks to model, build, populate, review, or refine their company, personas, operating contexts, stakeholders, goals, expectations, strategy, initiatives, metrics, beliefs, Jobs-to-be-Done, or value proposition in Cisely, follow the packaged skill:
- Read
skills/cisely-agency-model/SKILL.md(worldview, build order, MCP tool playbook) and itsreferences/. - For custom strategy kinds, read
skills/cisely-sub-strategy/SKILL.md.
Hard dependency: all authoring happens through the cisely MCP server
(https://app.cisely.dev/mcp, configured in .cursor/mcp.json). If its tools
aren't available, stop and ask the user to connect it in Cursor Settings → MCP —
never fabricate business data or write it to files instead.
Operate with high rigor: every node moves Draft → Revise → Activate; a declined
persona/expectation is a deliberate decision; refer to MCP tools by name
(CreatePersona, SituateStakeholder, …). Steer toward the payoff — a strategy
that roots in the same beliefs the stakeholders hold.
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 · 26 lines · 45 tokens per session scan A 8da2320352bf
cisely-agency-model is a cursor rule published in the GitHub repository CiselyAI/agency-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 355 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-31.
Other cursor rules, from other repositories
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.