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.
git 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/commands/floka-as/floka-marketplace/parallel)<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/parallel"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/parallel/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/commands/floka-as/floka-marketplace/parallel"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/parallel.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.00021 | $0.01247 |
| Opus 5 | $0.00010 | $0.00624 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
parallel 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 9d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge: Parallel
For work too big for a single context. Decomposes into independent streams, each in its own git worktree running /forge:auto autonomously. You get parallel builders with skeptical evaluators, isolated by git worktree.
Process
1. Discuss & Decompose
Start the same as /forge:contract — discuss gray areas with the user. But instead of one contract, you're scoping the whole feature and breaking it into independent work streams.
Decomposition rules:
- Each stream must be independently mergeable (no circular dependencies)
- No two streams touch the same file — this is critical for parallel worktrees. If two streams need the same file, either combine them or sequence them.
- Each stream should be a coherent unit: "backend API for X", "frontend views for X", "agent tools for X"
- Prefer 2–4 streams. More than 5 is usually over-decomposed.
Think in layers:
- Backend models + API → Stream 1
- Frontend components + views → Stream 2 (depends on Stream 1's API contract)
- Agent / LLM tools → Stream 3 (independent if API exists)
- Tests / evals → Can be part of each stream, or a final stream
2. Write Contracts
Write a contract for EACH stream in .forge/contracts/<feature>-<stream>.md. Same format as /forge:contract but with an added section:
## Dependencies
- Depends on: <other stream name, or "none">
- API contract: <if this stream consumes another stream's API, document the expected shape>
## File Boundaries
- This stream ONLY touches:
- <path/to/files>
- Do NOT modify:
- <paths owned by other streams>
3. Write the Master Contract
Create .forge/contracts/<feature>.md as an umbrella:
# Contract: <feature name>
## Goal
<overall feature goal>
## Streams
| Stream | Contract | Dependencies | Status |
|--------|----------|--------------|--------|
| <name> | <contract file> | none | pending |
| <name> | <contract file> | stream-1 | pending |
## Merge Order
1. <stream with no dependencies>
2. <stream depending on 1>
3. ...
## Integration Criteria
- [ ] <criterion that only passes when all streams are merged>
- [ ] Project gates pass on the integration branch after all merges
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.
- 9d ago First seen · 136 lines · 21 tokens per session scan A 30e7d2a06167
parallel is a command published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,247 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 commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.