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 josix/agent-flow --skill agentsview-usagegit clone --depth 1 https://github.com/josix/agent-flowWrote 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/josix/agent-flow/agentsview-usage)<a href="https://agentmods.dev/skills/josix/agent-flow/agentsview-usage"><img src="https://agentmods.dev/badge/skills/josix/agent-flow/agentsview-usage/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/josix/agent-flow/agentsview-usage"><img src="https://agentmods.dev/badge/skills/josix/agent-flow/agentsview-usage.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.00055 | $0.01484 |
| Opus 5.5 | $0.00022 | $0.00594 |
| Sonnet 5.5 | $0.00011 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
agentsview-usage 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 1mo 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.
AgentsView Usage
Search prior session history effectively, interpret results accurately, and stay within token budgets.
Overview
The agentsview MCP server exposes prior AI coding agent session history (synced by the agentsview CLI into a local SQLite archive) as read-only search tools, started via agentsview mcp.
All five granted tools are accessed via the MCP prefix mcp__plugin_agent-flow_agentsview__*.
Owner: Riko (Explorer Agent) — Riko is the primary session-history search agent and owns interpretation of results. Consumers:
- Senku (Planner Agent) — leverages past approaches when designing an implementation strategy: "has a similar feature been built before, and how?"
- Lawliet (Reviewer Agent) — cross-verifies current handling against precedent: "does this change match or diverge from how similar changes were handled previously?"
Out of scope: Loid (Executor) and Alphonse (Verifier) do NOT have agentsview access by design. This preserves the write/verify separation and keeps write/verify agents focused on the current diff and verification commands, not historical recall.
When to Query Session History vs. Graph vs. Grep
| Trigger condition | Preferred approach |
|---|---|
| "How was a similar task handled before?" | AgentsView: search_sessions |
| "What was decided/done in a specific prior session?" | AgentsView: get_session_overview |
| "What exact messages/commands were used before?" | AgentsView: get_messages (paginated) |
| "Find prior mentions of a specific string/error/pattern" | AgentsView: search_content |
| "What sessions ran recently on this project?" | AgentsView: list_sessions |
| "What is the dependency structure of THIS project?" | Project graph (graphify-usage) |
"Find the string literal TODO: fix" in current files |
Grep |
| "What does a specific config key say in THIS project?" | Read the file directly |
AgentsView is not available (agentsview: available: false in state) |
Skip — proceed without session-history search |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 112 lines · 55 tokens per session scan A d2cf551632dc
agentsview-usage is a skill published in the GitHub repository josix/agent-flow (7 stars, last pushed 17d ago), licensed MIT. It adds 55 tokens to every session and 1,484 once invoked, about $0.0002 per session on Opus 5.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
agents-bridge
Skill "agents-bridge" from ellmos-ai/skills, covering agents-bridge — the lifeboat, auch: time capsule (deutsch), workflow & vorgehen and sicherheitsgrenzen.
context-anchor
Drop a working reference at any point in a session to prevent cascading context drift. Use when switching tasks, resuming after a break, or handing off between agents.
honcho
Configure and troubleshoot Honcho memory for Hermes.
unified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
pinecone-research
Agent RAG and long-term memory with Pinecone.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…