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/raintr91/processkit/business-impact-reviewnpx skills add raintr91/Processkit --skill business-impact-reviewgit clone --depth 1 https://github.com/raintr91/ProcesskitWrote 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/raintr91/processkit/business-impact-review)<a href="https://agentmods.dev/skills/raintr91/processkit/business-impact-review"><img src="https://agentmods.dev/badge/skills/raintr91/processkit/business-impact-review.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.00018 | $0.00722 |
| Opus 5 | $0.00009 | $0.00361 |
| Sonnet 5 | $0.00004 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
business-impact-review 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/business-impact-review
Read-only analysis by default. Do not implement fixes unless explicitly asked.
Checkout resolution
Cross-repo callers/callees:
| System id | Map |
|---|---|
legacy-* |
legacy-repos.local.json |
| Otherwise | platform-repos.local.json |
Missing/empty map or missing key → Gaps + /configure-repo-maps; never
guess paths. Then remind platform-dna codegraph:wire if needed. Ambiguous
matches → ask or Gaps.
Workflow
- Scope changed public/protected methods, routes, Jobs, Events, Listeners, Commands and Schedules from diff/user files.
- Search every direct and indirect caller; follow one hop beyond facade/dispatch/proxy boundaries.
- Trace each reachable vertical path:
Client/FE or Scheduler/Webhook
→ route/command/job
→ auth/middleware/context rewrite
→ controller/handler
→ service/domain
→ repository/model/database
→ event/listener/job/external API
→ response/error/status mapping
→ FE/consumer/next async hop
- Apply
risk-classes.md: authZ/IDOR, request bag, trust boundary, over-broad parse, null/empty, error collapsing, hardcode/magic, async context/idempotency, business rules, transactions and compatibility. - Report evidence and unsearched repos explicitly.
Required report
Summary / ship recommendation
Changed symbols
Horizontal callers
Vertical process paths
Findings: severity · class · evidence · impact · verify
Unsearched repos / residual risks
Targeted test plan
Accelerators (optional)
Route per intent (rule cross-repo-index.mdc): never one merged
workspace graph — always the correct per-repo index.
if CodeGraph available: changed symbols + callers + call graph — for repo X use
its own server `codegraph-<key>` (--project-root = X's checkout), never the
open repo's index; unindexed repo → report `cd <root> && codegraph init`
else: targeted repository search/read
if Docskit available: map process steps to CMP/CTR/FLOW docs via DOCSKIT_ROOT
(never CodeGraph for architecture Markdown)
else: repository conventions/search
IR / registry / generation questions → pointer kits
(CODEGENKIT_DOCS_ROOT, TESTKIT_DOCS_ROOT, TESTKIT_TESTS_ROOT)
if ArtifactGraph available: affected tags/registries/parity
(local-only — never a shared index for other repos)
else: model review from scoped evidence
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.
- 5d ago First seen · 91 lines · 18 tokens per session scan A 6622f51ed9eb
business-impact-review is a skill published in the GitHub repository raintr91/Processkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 722 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…