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 Floka-as/floka-marketplace --skill forgegit clone --depth 1 https://github.com/Floka-as/floka-marketplaceWrote 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/floka-as/floka-marketplace/forge)<a href="https://agentmods.dev/skills/floka-as/floka-marketplace/forge"><img src="https://agentmods.dev/badge/skills/floka-as/floka-marketplace/forge/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/floka-as/floka-marketplace/forge"><img src="https://agentmods.dev/badge/skills/floka-as/floka-marketplace/forge.svg" alt="Reviewed on agentmods" width="80" 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.00200 | $0.01439 |
| Opus 5 | $0.00100 | $0.00720 |
| Sonnet 5 | $0.00040 | $0.00288 |
| Haiku 4.5 | $0.00020 | $0.00144 |
Grade A, and why
forge 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 11d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge
Spec-driven autonomous development workflow for Claude Code. Forge treats the spec as the highest-leverage artifact: a build with a thorough spec gets the right thing on the first try; a build with a thin checklist passes checkboxes and misses intent.
When this skill activates
- The user wants to build a non-trivial change and would benefit from a spec rather than coding directly
- The user invokes any
/forge:*command - The user says things like "spec this out", "let's plan this properly", "I want autonomous build", "skeptical review", "decompose this into parallel streams"
For trivial changes (typo fixes, single-line config edits, obvious bugs), don't invoke forge — just do the work.
The commands
| Command | Use when |
|---|---|
/forge:contract <task> |
You have a feature/change idea and want a thorough spec before any code. Most-used command. |
/forge:auto <task> |
You want to define the work and come back to a finished result. Discusses → writes contract → builds → evaluates → fixes, autonomously. |
/forge:build <contract> |
A contract exists; implement against it with gates after each chunk. |
/forge:evaluate <contract> |
Completed work needs a skeptical fresh-context review against its contract. |
/forge:parallel <feature> |
Work is too big for one context; decompose into independent streams across git worktrees. |
/forge:pulse |
Snapshot of repo health — velocity, branches, contracts, recent evaluations. |
/forge:status |
Quick list of active contracts and their progress. |
The pattern
┌─────────────────────────────────────┐
│ /forge:contract │
│ scout code → research libraries │
│ → discuss gray areas → spec │
└─────────────────────────────────────┘
│
▼
┌─────────────────────────────────────┐
│ /forge:build (or /forge:auto) │
│ implement chunk → run gates → │
│ evidence → checkbox → commit │
└─────────────────────────────────────┘
│
▼
┌─────────────────────────────────────┐
│ /forge:evaluate │
│ fresh-context sub-agent verifies │
│ ACCEPT / NEEDS WORK │
└─────────────────────────────────────┘
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.
- 11d ago First seen · 120 lines · 0 tokens per session scan A 96c8c15b6498
forge is a skill published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 200 tokens to every session and 1,439 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…