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 CATWILLgh/MAINFRAME --skill pi-business-analysisgit clone --depth 1 https://github.com/CATWILLgh/MAINFRAMEWrote 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/catwillgh/mainframe/pi-business-analysis)<a href="https://agentmods.dev/skills/catwillgh/mainframe/pi-business-analysis"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/pi-business-analysis.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.00055 | $0.00475 |
| Opus 5 | $0.00028 | $0.00237 |
| Sonnet 5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
pi-business-analysis 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mainframe-pi-business-analysis — 86% identical, 17 lines differ
What it actually says
Pi business analysis
Keep ownership of user communication and product decisions in this primary
session. Pi is a read-only external worker that writes one evidence-grounded
Markdown review under docs/initiatives/<slug>/reviews/; it does not replace
the final decision or definition of done.
Use the current project as the analysis boundary. Choose one short stable
initiative slug. Pass only the requirements input explicitly handed over for
this review: --statement for the supplied short text, repeatable --entry
for named files inside the project, and repeatable --input-file for named
external files. Pass supplied statement text verbatim; do not summarize or
rewrite it. These forms may be combined into one bounded package. Do not
infer the package from ordinary conversation, planning context, or unrelated
session history. Do not invent a source path or broaden the project root. If no
explicit source was handed over, do not run the worker.
Build the command with concrete values. When the invocation supplied complete arguments, use:
mainframe-pi business-analysis $ARGUMENTS
If no --initiative arrived with the invocation, choose the slug from the
current agreed direction and run the same command with that concrete slug. Do
not pass an empty or literal placeholder.
The command may run for several minutes. Let it finish once; do not start a
second fresh run merely because it is slow. After completion, inspect the JSON
result and the reported review file. Treat incomplete as usable but limited
evidence, and blocked or a non-zero exit as a failed run. Report the review
path, run status, readiness, and material limitations plainly. Never present a
partial or missing review as completed analysis.
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 · 42 lines · 55 tokens per session scan A aef4271e15a7
pi-business-analysis is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 16d ago), licensed MIT. It adds 55 tokens to every session and 475 once invoked, about $0.0003 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
at-vision
Inspect screenshots, photos, diagrams, image paths, and image URLs when the task depends on visible content. Use when the prompt lacks actual image content, native inspection fails, or the user requests inspectimage; prefer the MCP tool, then the installed CLI.
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
review-pr
Perform a comprehensive code review of a pull request.
guide-recap
Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate release notes, announcements, social media posts, or recap summaries from guide updates.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.