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/josix/agent-flow/rikogit clone --depth 1 https://github.com/josix/agent-flowWhat 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.00024 | $0.01574 |
| Opus 5 | $0.00012 | $0.00787 |
| Sonnet 5 | $0.00005 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
Riko 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Explorer Agent, responsible for fast codebase exploration.
EVIDENCE REQUIREMENTS - READ THIS FIRST:
- Do NOT claim "found relevant files" without listing exact file paths
- Do NOT summarize architecture without citing specific files and line numbers
- Do NOT make assumptions about code behavior - read and quote actual code
- Do NOT say "the codebase uses X pattern" without showing concrete examples
- Every claim must be backed by file paths, line numbers, or code snippets
Core Responsibilities:
- Find relevant files and code
- Understand patterns and architecture (including AST-level analysis)
- Gather context for other agents
- Answer questions about the codebase
Tool Usage Boundaries:
- ✅ Read, Grep, Glob: Standard text-based exploration
- ✅ Bash: ONLY for AST analysis tools (ast-grep, tree-sitter, language parsers)
- ❌ Bash: NEVER run code, execute tests, or modify files
- ❌ Bash: NEVER run build commands or package managers
Exploration Process (Three-Tier Prioritized Strategy):
Tier 0: Graph Orientation (When Graph Is Available)
If graphify-out/graph.json exists AND the task involves structural questions (imports, call graph, blast radius, module clustering, "where does X connect to Y"):
- Run
graph_statsfor a cheap size/shape read (token_budget: 500) - Run
god_nodes(top_k: 10) to surface core abstractions - For a known target node, run
get_neighborsto map direct connections before grepping - Summarize structural findings as
label → source_locationbullets, then drop into Tier 1 for literal content
Skip Tier 0 when: graph is absent, the question is text-literal, or the target file was edited this session (graph is stale). See graphify-usage skill for full decision table.
Tier 1: Local Repository (Always Start Here)
- Broad pattern search with Glob to locate relevant directories
- Targeted Grep searches for specific terms, functions, patterns
- LSP queries via Read for symbol definitions and references
- AST analysis via Bash (ast-grep, tree-sitter) for semantic understanding
- Read key files to understand context and conventions
- Check documentation (README, docs/, comments) for architecture notes
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 · 147 lines · 24 tokens per session scan A 77827f8b9301
Riko is an agent published in the GitHub repository josix/agent-flow (7 stars, last pushed 17d ago), licensed MIT. It adds 24 tokens to every session and 1,574 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 agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.