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/is-bo/fullstack-forge-skill/forge-requirementsnpx skills add is-bo/fullstack-forge-skill --skill forge-requirementsgit clone --depth 1 https://github.com/is-bo/fullstack-forge-skillWhat 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.00339 |
| Opus 5 | $0.00010 | $0.00169 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
forge-requirements 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.
This is a copy
86% identical to forge-feature — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Fullstack Forge adapter: forge-requirements
This file is a pointer maintained by Fullstack Forge. It exists so this agent host can discover and trigger the skill. The full playbook is not duplicated here: one canonical copy is shared by every installed host.
Read the canonical playbook now and follow it exactly:
../../../.fullstack-forge/skills/forge-requirements/SKILL.md
That path is relative to this file. From the installation root it is
.fullstack-forge/skills/forge-requirements/SKILL.md. Every resource the playbook references
(fullstack-forge/references/..., fullstack-forge/schemas/...,
fullstack-forge/templates/..., fullstack-forge/profiles/...) resolves relative to
.fullstack-forge/skills/.
The canonical playbook owns any deterministic composition step; perform that step exactly
once. This adapter never adds a second workflow or composition command.
Do not edit this adapter; edit the canonical playbook instead. If the canonical file is
missing or unreadable the installation is damaged. Report it and repair through the same
project-package, archive, or plugin mechanism that installed this adapter. Never fall back to
an unpinned npx forge, which may resolve an unrelated public package.
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 · 30 lines · 21 tokens per session scan A 002aee918f68
forge-requirements is a skill published in the GitHub repository is-bo/fullstack-forge-skill (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 21 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to forge-feature, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
agent-evaluation-reporting
Use when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
adhx
Fetch any X/Twitter post as clean LLM-friendly JSON. Converts x.com, twitter.com, or adhx.com links into structured data with full article content, author info, and engagement metrics. No scraping or browser required.
agent-memory
A hybrid memory system that provides persistent, searchable knowledge management for AI agents.
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…