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/invoke)<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/invoke"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/invoke/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/invoke"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/invoke.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.00039 | $0.01147 |
| Opus 5 | $0.00019 | $0.00574 |
| Sonnet 5 | $0.00008 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
invoke 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 10d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Examples:
/board:invoke naval should we raise prices/board:invoke walling jump math — 50k consulting, 200k personal cash/board:invoke gary --ask(surfaces Gary's characteristic questions for the user to answer)
Step 1: Locate the board
Check for .claude/board.md then ~/.claude/board.md. If neither exists, respond:
"No board found. Run
/board:buildfirst to compose one — takes about 5 minutes."
Stop.
Step 2: Resolve the advisor
Match the first argument against advisor names in the board's ## Members section (case-insensitive, partial match — "naval" matches "Naval Ravikant"). If multiple match, pick the most-likely one and note: "Matched ''. (Disambiguate with full name if you meant another.)"
If no match, list the advisors on the user's board and stop.
Step 3: Read the advisor's entry
Read the relevant section of the board file in full. Note:
- Voice line (if attributed)
- Frameworks
- When to invoke (sanity check: is this the right advisor for this topic? If clearly mismatched, suggest a better fit but proceed if the user explicitly chose this advisor.)
- Characteristic questions
- Counterweight-to mapping
- Won't help with / hand-off
Step 4: Decide the response shape
If --ask was passed: skip to Step 5b.
If the topic is missing or one-word vague (e.g. just "pricing", just "growth"): default to a brief response (2–3 sentences) followed by 2–3 characteristic questions. Don't try to advise on something underspecified.
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.
- 10d ago First seen · 112 lines · 39 tokens per session scan A 48dfe372f006
invoke is a command published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,147 once invoked, about $0.0002 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.