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 sairam0424/MindForge --skill mindforge-workstreamsgit 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/skills/sairam0424/mindforge/mindforge-workstreams)<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-workstreams"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-workstreams/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/sairam0424/mindforge/mindforge-workstreams"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-workstreams.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.00024 | $0.00517 |
| Opus 5 | $0.00012 | $0.00259 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
mindforge-workstreams 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 7d 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
/mindforge-workstreams
Manage parallel workstreams for concurrent milestone work.
Usage
/mindforge-workstreams [subcommand] [args]
Subcommands
| Command | Description |
|---|---|
list |
List all workstreams with status |
create <name> |
Create a new workstream |
status <name> |
Detailed status for one workstream |
switch <name> |
Set active workstream |
progress |
Progress summary across all workstreams |
complete <name> |
Archive a completed workstream |
resume <name> |
Resume work in a workstream |
Step 1: Parse Subcommand
Parse the user's input to determine which workstream operation to perform.
If no subcommand given, default to list.
Step 2: Execute Operation
list
Run: node "$MindForge_TOOLS" workstream list --raw --cwd "$CWD"
Display the workstreams in a table format showing name, status, current phase, and progress.
create
Run: node "$MindForge_TOOLS" workstream create <name> --raw --cwd "$CWD"
After creation, display the new workstream path and suggest next steps:
/mindforge-new-milestone --ws <name>to set up the milestone
status
Run: node "$MindForge_TOOLS" workstream status <name> --raw --cwd "$CWD"
Display detailed phase breakdown and state information.
switch
Run: node "$MindForge_TOOLS" workstream set <name> --raw --cwd "$CWD"
Also set MindForge_WORKSTREAM env var for the current session.
progress
Run: node "$MindForge_TOOLS" workstream progress --raw --cwd "$CWD"
Display a progress overview across all workstreams.
complete
Run: node "$MindForge_TOOLS" workstream complete <name> --raw --cwd "$CWD"
Archive the workstream to milestones/.
resume
Set the workstream as active and suggest /mindforge-resume-work --ws <name>.
Step 3: Display Results
Format the JSON output from mindforge-tools into a human-readable display.
Include the ${MindForge_WS} flag in any routing suggestions.
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.
- 7d ago First seen · 66 lines · 24 tokens per session scan A bdaccb93c0b8
mindforge-workstreams is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 517 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-09-03.
Other skills, from other repositories
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
accelo-automation
Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.
aero-workflow-automation
Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas.
agiled-automation
Automate Agiled tasks via Rube MCP (Composio). Always search tools first for current schemas.
atlassian-automation
Automate Atlassian tasks via Rube MCP (Composio). Always search tools first for current schemas.
bigpicture-io-automation
Automate Bigpicture IO tasks via Rube MCP (Composio). Always search tools first for current schemas.