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 DevRik99/forge-mcp --skill unlazygit clone --depth 1 https://github.com/DevRik99/forge-mcpWrote 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/devrik99/forge-mcp/unlazy)<a href="https://agentmods.dev/skills/devrik99/forge-mcp/unlazy"><img src="https://agentmods.dev/badge/skills/devrik99/forge-mcp/unlazy.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.00100 | $0.01443 |
| Opus 5 | $0.00050 | $0.00722 |
| Sonnet 5 | $0.00020 | $0.00289 |
| Haiku 4.5 | $0.00010 | $0.00144 |
Grade A, and why
unlazy 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
27 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .github/workflows/test.yml 726 B
- .gitignore 153 B
- agents/openai.yaml 250 B
- CHANGELOG.md 6.2 KB
- CONTRIBUTING.md 4.2 KB
- LICENSE 1.0 KB
- package.json 376 B
- README.md 14 KB
- references/gates.md 8.9 KB
- references/method.md 3.0 KB
- references/orchestration.md 5.5 KB
- references/parallel.md 5.9 KB
- references/token-economy.md 2.5 KB
- research/validation-protocol.md 4.3 KB
- scripts/gate-check.mjs 28 KB runs code
- scripts/install-hooks.mjs 6.2 KB runs code
- scripts/lib/gates.mjs 22 KB runs code
- scripts/lib/regex-worker.mjs 282 B runs code
- scripts/stop-hook.mjs 5.3 KB runs code
- SECURITY.md 6.0 KB
- templates/gates-leaf.md 2.0 KB
- templates/gates-node.md 1.9 KB
- templates/PLAN.md 2.3 KB
- tests/hardening-tests.mjs 21 KB runs code
- tests/run-tests.mjs 20 KB runs code
- tests/self-check.mjs 4.8 KB runs code
- tests/stress-tests.mjs 12 KB runs code
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.
- 4d ago First seen · 91 lines · 100 tokens per session scan A 1c3ebe9ef610
unlazy is a skill published in the GitHub repository DevRik99/forge-mcp (0 stars, last pushed yesterday), with no licence file. It adds 100 tokens to every session and 1,443 once invoked, about $0.0005 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
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.