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 Firstp1ck/pi-coding-agent-forge --skill feature-development-workflowgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-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/firstp1ck/pi-coding-agent-forge/feature-development-workflow)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/feature-development-workflow"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/feature-development-workflow/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/firstp1ck/pi-coding-agent-forge/feature-development-workflow"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/feature-development-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01864 |
| Opus 5.5 | $0.00019 | $0.00746 |
| Sonnet 5.5 | $0.00010 | $0.00373 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
feature-development-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development Workflow
Use this skill for a user-authorized request to deliver a new capability. It preserves decision, implementation, review, and completion evidence while scaling the process to the feature's actual risk and scope. It is guidance, not a runtime guard: loading this skill does not install a package, enable an integration, change settings, or create hard enforcement.
When to Use
Use when the request adds a user-visible, product, system, interface, workflow, or integration capability and the agent is expected to implement it.
Do not use for:
- Bug fixes that restore documented or intended existing behavior.
- Refactors with no new capability.
- Documentation-only, test-only, formatting-only, or dependency-maintenance work.
- Planning, research, review, troubleshooting, incident response, operations, or a question without requested feature delivery.
- Installation, enablement, publication, deployment, or configuration changes unless that action is separately authorized.
Should trigger
- “Add a workspace export feature with authorization rules and a CSV download.”
- “Implement a new notification preference channel and migrate existing defaults.”
- “Create a small user-facing toggle that enables the requested display behavior.”
- “Build this new integration endpoint and deliver it with tests.”
Should not trigger
- “Fix the crash when an empty CSV is uploaded.”
- “Refactor the cache module without changing behavior.”
- “Add API documentation and unit tests for the existing endpoint.”
- “Research options for notification providers before we choose one.”
- “Review this pull request for security issues.”
Ambiguous requests
A request such as “add a tiny flag” may be a feature, a bug fix, or a configuration change. Inspect the affected behavior and user intent before routing. If it is feature delivery, classify it; otherwise use the workflow appropriate to the actual task.
Invocation Design
- Invocation mode: model-invoked after explicit package enablement.
- Leading concept: feature implementation workflow.
- Route only when delivery of a new capability is requested; do not use this as a catch-all engineering process.
- Creation of this package is inert. Review it before any later installation or enablement, which requires explicit authorization.
What ships with it
2 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.
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 Changed · +3 lines c64450743702
- 1mo ago First seen · 121 lines · 48 tokens per session scan A be5cc80db4eb
feature-development-workflow is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (91 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,864 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
npm-docs
Use this skill whenever the user asks about npm, package management, publishing packages, semantic versioning, npm CLI commands, or Node.js dependencies. Covers npm 12.x including the registry, scopes, organizations, security (audit, provenance, 2FA), CI/CD integration, workspaces, scripts, .npmrc configuration, and…
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
dependency-manager
Manage project dependencies — update packages, audit vulnerabilities, resolve conflicts, and keep dependencies healthy. Use when updating packages, fixing vulnerability alerts, or resolving dependency issues.
colab-finetuning
Fine-tune LLMs on Google Colab GPUs directly from openscience. Connects to Colab runtimes via WebSocket bridge for remote training with Unsloth. Supports SFT, GRPO, DPO, vision, and TTS workflows on free T4 to Pro A100 GPUs.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…