Forge is a command-line development environment that uses AI models as a pair programmer for working with code and shell commands. Developers use it to understand projects and carry out coding tasks through interactive, one-shot, or ZSH-based workflows. The catalogue entries extend Forge with reusable skills, agents, commands, and instructions.
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 tailcallhq/forgecode --skill resolve-fixmegit clone --depth 1 https://github.com/tailcallhq/forgecodeWrote 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/tailcallhq/forgecode/resolve-fixme)<a href="https://agentmods.dev/skills/tailcallhq/forgecode/resolve-fixme"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/resolve-fixme/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/tailcallhq/forgecode/resolve-fixme"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/resolve-fixme.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.00100 | $0.00963 |
| Opus 5.5 | $0.00040 | $0.00385 |
| Sonnet 5.5 | $0.00020 | $0.00193 |
| Haiku 4.5 | $0.00010 | $0.00096 |
Grade A, and why
resolve-fixme 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resolve-fixme — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve FIXME Comments
Workflow
1. Run the discovery script
Execute the script from the repository root to collect all FIXMEs with context:
bash .forge/skills/resolve-fixme/scripts/find-fixme.sh [PATH]
PATHis optional; omit it to search the entire working directory.- The script prints each FIXME with 2 lines of context before and 5 lines after, along with the exact file path and line number.
- Skips
.git/,target/,node_modules/, andvendor/. - Requires either
rg(ripgrep) orgrep+python3.
2. Expand each FIXME into its full instruction
Do not rely on the discovery output alone.
For every hit:
- Open the file and read around the reported line.
- Expand the FIXME to include the entire comment block.
- Treat all consecutive related comment lines as part of the same instruction.
Important:
- A FIXME may be multiline. The line containing
FIXMEis often only the beginning. - The real instruction may continue on following comment lines and may contain the actual implementation details.
- Do not interpret or edit a FIXME until you have read the full block.
For each expanded FIXME, capture:
- file path
- start line and end line of the full comment block
- a short summary of what that FIXME is asking for
3. Consolidate related FIXMEs across files
Before editing code, review all expanded FIXMEs together.
Many FIXMEs describe different facets of the same underlying task across multiple files. For example:
- one file may describe a domain type that needs to be introduced
- another may describe a parameter that should disappear once that type exists
- another may describe a service, repo, or UI update needed to complete the same refactor
Group such FIXMEs into a single implementation task.
When grouping, look for:
- shared vocabulary
- references to the same type, service, repo, parameter, or feature
- comments that clearly describe prerequisite and follow-up changes in different files
- comments that only make sense when read together
What ships with it
1 file 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.
- 1mo ago First seen · 111 lines · 100 tokens per session scan A 5e3cfde0c22a
resolve-fixme is a skill published in the GitHub repository tailcallhq/forgecode (7,638 stars, last pushed today), licensed Apache-2.0. It adds 100 tokens to every session and 963 once invoked, about $0.0004 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
agent-observability
Instrument AI agents with tracing, token metrics, latency, and cost visibility. Use for reliability and debugging.
accesslint-audit
Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to a browser-MCP composition or HTML-string audits.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
api-analyzer
Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params).
accesslint-scan
Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.