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.
git clone --depth 1 https://github.com/sairam0424/MindForgeWrote 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/commands/sairam0424/mindforge/healthcare)<a href="https://agentmods.dev/commands/sairam0424/mindforge/healthcare"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/healthcare/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/commands/sairam0424/mindforge/healthcare"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/healthcare.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.00045 | $0.00517 |
| Opus 5 | $0.00023 | $0.00259 |
| Sonnet 5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
mindforge:healthcare 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
<execution_context> @.mindforge/skills/healthcare-systems/SKILL.md </execution_context>
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 · 32 lines · 45 tokens per session scan A f98289e69247
mindforge:healthcare is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 517 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-09-03.
Other commands, from other repositories
p7-release-docs
Creates all user-facing documents for the launch: release notes, user guide or onboarding materials, and the legally required mandatory documents (privacy policy, legal notice). These documents must be available before go-live.
p1-privacy
Conducts a systematic initial assessment of data protection requirements: What personal data is processed, on what legal basis, and what DSGVO (GDPR) obligations arise from this? The result is a well-founded DSGVO initial assessment as a mandatory component of the Concept.
p2-regulatory-check
Validates the regulatory Assumptions from Phase 1 concretely and practically: Is the venture legally implementable? Which hurdles are real, which are surmountable? The result is a robust regulatory validation as the Decision basis for Gate 2.
p3-arch-components
Creates the system architecture overview with component diagram, responsibilities and data flows.
p3-sec-api
Defines input validation, rate limiting, CORS and security headers.
p6-audit-dsgvo
Compares the implementation against the DSGVO initial assessment: data subject rights, data minimisation, deletion deadlines, data processing agreements.