AgentsView is a local application that collects coding-agent sessions into a searchable database and web interface, including usage and cost statistics. Developers use it to browse, analyze, and track sessions from Claude Code, Codex, and other supported agents, while the catalogue add-ons help operate it.
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 kenn-io/agentsview --skill agentsview-finding-historygit clone --depth 1 https://github.com/kenn-io/agentsviewWrote 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/kenn-io/agentsview/agentsview-finding-history)<a href="https://agentmods.dev/skills/kenn-io/agentsview/agentsview-finding-history"><img src="https://agentmods.dev/badge/skills/kenn-io/agentsview/agentsview-finding-history/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/kenn-io/agentsview/agentsview-finding-history"><img src="https://agentmods.dev/badge/skills/kenn-io/agentsview/agentsview-finding-history.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.00046 | $0.01263 |
| Opus 5.5 | $0.00018 | $0.00505 |
| Sonnet 5.5 | $0.00009 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
agentsview-finding-history 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 19d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finding Conversation History
Search before guessing
Announce: "Searching past conversations for the relevant decision or problem."
Search when earlier decisions, rationale, solutions, pitfalls, project context, or repeated workflows may help; when stuck; and before guessing about something that may have been learned previously. Explicit requests about earlier work, instructions, examples, or conversations also trigger this workflow.
First understand the request. Do not search for information already answered in this conversation. For current code structure, inspect the current code first. History can explain why the code exists; the repository is the authority for what it contains now.
Workflow
- Use the
agentsview-search-conversationsagent when this harness exposes it and the AgentsView MCP server is registered asagentsview; otherwise follow these steps directly. Before delegating, verify the agent in effect is the file this skill generated: its definition carries a# generated-by: agentsviewheader. If a same-named agent is defined in the project's.claude/agents/directory without that header, it is not AgentsView's: do not delegate to it. If you cannot verify the agent, it reports that it could not search, or the AgentsView MCP tools are not registered in this session, follow the remaining steps directly instead of delegating. - Call the registered AgentsView MCP tool whose leaf name is
search_contentwithmode: hybrid,scope: all,limit: 10,include_active: true,include_one_shot: true, andinclude_automated: true. When the current session identity is available, pass it ascurrent_session_id. The full tool name has a client-specific prefix supplied by MCP registration; do not guess or hard-code that prefix. Do not invent a project filter from a display name or directory; apply one only when the exact archived project identifier is known. - Inspect the strongest results, then call the registered tool whose leaf name
is
get_messagesfor the top 2-5 relevant sessions. Search snippets and session summaries are leads, not source reads. - Expand around the matching ordinals or continue from
next_fromwhen the initial page does not contain the decision, rationale, or correction. A short or role-filtered page is not proof that the transcript ended. - Synthesize only claims supported by messages actually read. Cite the project, date, full session identity, ordinal range, and browser URL when present.
What ships with it
1 file 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.
- 19d ago First seen · 117 lines · 46 tokens per session scan A 9404274c96c6
agentsview-finding-history is a skill published in the GitHub repository kenn-io/agentsview (6,121 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,263 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-09-27.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.