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 chaussky/ainalyst --skill requirements_assess_changesgit 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/requirements_assess_changes)<a href="https://agentmods.dev/skills/chaussky/ainalyst/requirements_assess_changes"><img src="https://agentmods.dev/badge/skills/chaussky/ainalyst/requirements_assess_changes/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/chaussky/ainalyst/requirements_assess_changes"><img src="https://agentmods.dev/badge/skills/chaussky/ainalyst/requirements_assess_changes.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.00098 | $0.02238 |
| Opus 5.5 | $0.00039 | $0.00895 |
| Sonnet 5.5 | $0.00020 | $0.00448 |
| Haiku 4.5 | $0.00010 | $0.00224 |
Grade A, and why
requirements_assess_changes 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 1mo 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
1 file 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.
- 1mo ago First seen · 216 lines · 98 tokens per session scan A 9f7cf11a6414
requirements_assess_changes is a skill published in the GitHub repository chaussky/ainalyst (48 stars, last pushed 1mo ago), licensed AGPL-3.0. It adds 98 tokens to every session and 2,238 once invoked, about $0.0004 per session on Opus 5.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-plausibleba
Use this skill when someone wants to run a complete business architecture session — producing a Capability Map, Concept Model, and Value Stream in one guided flow. Trigger on phrases like: "run PlausibleBA", "build my business architecture", "I want a full BA model", "run all three", or when someone invokes…
consistency-check
Verifies the V-Model artifact graph: Epics, Features, ADRs, PLANs, Backlog, Wayfinder rows, code refs. Syntactic and semantic modes. Explicit user command for "consistency check", "graph check", "dead links", "orphan features", or before a release; routine enforcement runs via the pre-commit hook, not per phase.
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…
account-plan
Use when pursuing, defending, expanding, or recovering a client account or project opportunity. Use when applying the Account Plan consulting method and when a user asks for Account Plan, method execution, structured diagnosis, or action planning.
force-field-analysis
Use when adoption, stakeholder support, or organizational movement depends on shifting incentives and resistance. Use when applying the Force Field Analysis consulting method and when a user asks for Force Field Analysis, method execution, structured diagnosis, or action planning.
raci-matrix
Use when ownership, approval rights, handoffs, or decision authority are unclear. Use when applying the RACI Matrix consulting method and when a user asks for RACI Matrix, method execution, structured diagnosis, or action planning.