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 skills/chaussky/ainalyst/change_strategynpx skills add chaussky/ainalyst --skill change_strategygit clone --depth 1 https://github.com/chaussky/ainalystWrote 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/chaussky/ainalyst/change_strategy)<a href="https://agentmods.dev/skills/chaussky/ainalyst/change_strategy"><img src="https://agentmods.dev/badge/skills/chaussky/ainalyst/change_strategy.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 | $0.00107 | $0.03122 |
| Opus 5 | $0.00053 | $0.01561 |
| Sonnet 5 | $0.00021 | $0.00624 |
| Haiku 4.5 | $0.00011 | $0.00312 |
Grade A, and why
change_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 4d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 296 lines · 107 tokens per session scan A c12dff9ad91f
change_strategy is a skill published in the GitHub repository chaussky/ainalyst (41 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 107 tokens to every session and 3,122 once invoked, about $0.0005 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
ba-concept-model
Use this skill whenever a business analyst, architect, or project team needs to identify, define, and structure the core business objects (concepts) of a domain — even if they don't use that exact term. Trigger on phrases like: "what are the key things the business manages", "define our business objects", "build a…
ba-taxonomy-standard
Shared conventions used across all PlausibleBA skills. Load this skill whenever producing, validating, or comparing any PlausibleBA taxonomy — Capability Maps, Concept Models, Value Streams, or any other structured artefact. It defines the numbering system, column order, naming conventions, MECE rules, and XLSX…
business-analysis
Condenses a structured dialog about problem, users, and scope into a short BA record that feeds requirements engineering. Use when the user mentions "Business Analysis", "BA", "Problem Analysis", "Personas", "Define Scope", "Explore", "How might we", "Value Proposition", or starts a new project without a clear…
requirements-engineering
Transforms business analyses into epics, features, and tech-agnostic success criteria; creates the architect handoff. Use when the user mentions "Requirements", "RE", "Define Features", "Create Epics", "User Stories", "Success Criteria", "NFRs", "ASRs", "Acceptance Criteria", or when a BA exists and needs…
project-conventions
Defines project structure, naming conventions, and way of working for all projects; other skills link here for the canonical specs. Use when the user mentions "project setup", "project structure", "conventions", "init", "initialize project", "directory structure", or starts a new project.
business-requirements-analyst
Complete methodology for software and business requirements gathering. Use when you need to document a new project, validate a business idea, create technical specifications, or generate complete documentation covering business vision, stakeholders, processes, functional and non-functional requirements, data model…