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 agents/lukacf/meerkat/force-runnergit clone --depth 1 https://github.com/lukacf/meerkatWhat 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.00056 | $0.00274 |
| Opus 5 | $0.00028 | $0.00137 |
| Sonnet 5 | $0.00011 | $0.00055 |
| Haiku 4.5 | $0.00006 | $0.00027 |
Grade A, and why
force-runner 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 2d 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.
What it actually says
You are The Force runner - dispatch tasks to AI models via work_with.
Tool:
work_with(agent, task, session_id)- Spawn CLI agent that can read files, run commands, work autonomously
Models:
gpt-5.5,gpt-5.4,gpt-5.4-mini,gpt-5.4-pro,gpt-5.3-codex- OpenAIgemini-3.5-flash,gemini-3.1-pro-preview- Googleclaude-opus-4-8,claude-sonnet-4-5- Anthropic
Rules:
- Always use
work_with- it spawns an agentic CLI with file/command access - Always provide descriptive
session_idfor conversation continuity - Pick the right model for the task
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.
- 2d ago First seen · 21 lines · 56 tokens per session scan A b7e94ead812b
force-runner is an agent published in the GitHub repository lukacf/meerkat (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 274 once invoked, about $0.0003 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-30.
Other agents, from other repositories
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
maintainer-orchestrator-design
This document explains the thinking behind the deerflow-maintainer-orchestrator skill: what it is for, the boundaries that make it safe to run, and the principles that shape how it reviews. It is written for DeerFlow maintainers who run the skill, and for anyone in the community who wants to understand — or adapt …
delegation
A SubAgent is an ephemeral child run spawned by a parent agent that inherits the parent's identity by default: same agent alias, same SecurityPolicy, same memory allowlist, same configured model provider, same tool registry. Auditable as a child via a tracing span agent. .subagent. .
internals
This page is the architecture-depth companion to the rest of the Agents section: how the runtime enforces per-agent permissions, scopes memory, and attributes logs. For configuring and running agents, start at Agents; for the schema-level field reference, see Config; for live setup steps, see Multi-agent setup.
anatomy
An agent is configured as a single [agents. ] block. Every field is either a reference to something configured elsewhere or a per-agent override. The table below is generated from the config schema, so it always matches the running build. Click a field to expand it; click again to see how to set it.