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 agentmods add skills/guorunjie/skillpack-forge/skillpack-forge-developernpx skills add guorunjie/skillpack-forge --skill skillpack-forge-developergit clone --depth 1 https://github.com/guorunjie/skillpack-forgeWrote 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/guorunjie/skillpack-forge/skillpack-forge-developer)<a href="https://agentmods.dev/skills/guorunjie/skillpack-forge/skillpack-forge-developer"><img src="https://agentmods.dev/badge/skills/guorunjie/skillpack-forge/skillpack-forge-developer.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 | $0.00021 | $0.00224 |
| Opus 5 | $0.00010 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
skillpack-forge-developer 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 3d 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
skillpack-forge-developer
Generated from skillpack.yaml by Skillpack Forge.
Project
Compile one repo manifest into portable AGENTS.md, AI coding skills, agent rules, and CI checks.
Workflow
- Inspect the current project context and nearby files
- Run npm test before completion
- Document any command that cannot be run
Commands
- install:
npm install - test:
npm test - compile:
npm run compile - doctor:
npm run doctor - scan:
npm run scan - diff:
npm run diff - check:
npm run check - mcpb:
npm run mcpb - templates:
npm run templates - import-json:
npm run import-json - demo:
npm run demo
Principles
- Preserve user changes and keep edits scoped
- Inspect the current repo state before changing files
- Run verification before claiming success
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.
- 3d ago First seen · 35 lines · 21 tokens per session scan A 7ea883dcc514
skillpack-forge-developer is a skill published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 224 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-08-31.
Other skills, from other repositories
healthcare-agents
Healthcare Agents plugin router for healthcare administration work. Use when the user says to use the Healthcare Agents plugin, asks for a healthcare administration workup, names a department or area such as revenue cycle, quality, compliance, clinical administration, payer, health IT, population health, pharmacy…
lowkey-effort
Automatically calibrate response effort and token usage to match task complexity. Use this skill at the START of every response to classify the incoming task and select the appropriate effort tier before generating any output. Trigger whenever you're about to answer a question or complete a task — this skill saves…
plan-task
Create a detailed implementation plan before coding. Use when starting a new feature, multi-step refactor, or complex task. Invoked by saying "plan", "create a plan", or "plan this task".
commit
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push".
document-task
Document completed work — update task log, sync documentation, log observations. Use after finishing a task or batch of changes.
commit-all
Batch-commit all uncommitted changes grouped by relevance. Use when multiple accumulated changes need committing. Invoked by saying "commit all" or "commit everything".