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-remove-workspacegit 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-remove-workspace)<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-remove-workspace"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-remove-workspace/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-remove-workspace"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-remove-workspace.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.00016 | $0.00150 |
| Opus 5.5 | $0.00006 | $0.00060 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
mindforge-remove-workspace 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.
What it actually says
<execution_context> @.agent/workflows/mindforge-remove-workspace.md @docs/References/ui-brand.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.
- 1mo ago First seen · 23 lines · 16 tokens per session scan A 67311c2c8e5e
mindforge-remove-workspace is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 8d ago), licensed MIT. It adds 16 tokens to every session and 150 once invoked, about $0.0001 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-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.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
development-scheduler
A workflow for coordinating multi-role coding work through Herdr, a task scheduler, and repo-harness sessions. It assigns implementation, review, and handoff tasks while checking permissions and evidence.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
monorepo-architect
Expert guide for designing and managing scalable monorepos using Turborepo, pnpm workspaces, and shared packages / Panduan ahli untuk merancang dan mengelola monorepo skalabel menggunakan Turborepo dan pnpm workspaces.
managing-github-issues
Logs, promotes, ranks, synthesizes and audits GitHub issues with dry-run-first, deduplicated, taxonomy-validated and secret-redacted payloads. Use to log repository friction, bugs or map debt as issues, promote a local tasks/.md note to an issue, rank issues P0-P3, draft a systemic refactoring proposal from friction…