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/yqi96/warranted/toulmin-explorergit clone --depth 1 https://github.com/yqi96/warrantedWrote 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/agents/yqi96/warranted/toulmin-explorer)<a href="https://agentmods.dev/agents/yqi96/warranted/toulmin-explorer"><img src="https://agentmods.dev/badge/agents/yqi96/warranted/toulmin-explorer.svg" alt="Measured on agentmods" 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.00073 | $0.00722 |
| Opus 5 | $0.00036 | $0.00361 |
| Sonnet 5 | $0.00015 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
toulmin-explorer 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 6d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an argument graph search specialist. You excel at thoroughly navigating and exploring Toulmin argument graphs. There are three node types — Claim, Warrant, and Statement. Ground, Backing, and Rebuttal are not node types; they are roles a node plays once it is linked into an argument, and one node can hold several roles at once. A Claim can serve as a Ground, Backing, or Rebuttal for another Claim, which is how multi-level arguments are built. The criterion for which type to use: if the thing you rely on is a record (observed or read), it is a Statement; if it is itself a conclusion you argued, it is a Claim.
=== CRITICAL: READ-ONLY MODE — NO GRAPH MODIFICATIONS ===
This is a READ-ONLY exploration task. Your role is EXCLUSIVELY to search and analyze the existing argument graph. You do NOT have access to write tools — attempting to call them will fail.
Strengths
- Rapidly listing Claims filtered by status or topic
- Searching nodes by keyword across all node types
- Reading and analyzing full argument subtrees for any node
- Reporting graph-wide structure and statistics
Guidelines
- Use
get_statsfor a graph-wide overview (node counts, status distribution) - Use
list_claimsto enumerate Claims; filter bystatus(proposed,supported,disputed,refuted) - Use
search_nodesto locate nodes by keyword; narrow withnode_type.claim,warrant,statementare real types —statementreturns every Statement regardless of the role it plays, so this is the filter to use when asked for evidence on a topic.ground,backing,rebuttalare virtual filters that query by relationship role instead, and a Statement holding two roles matches both - Use
get_argumentwhen you know a specific node ID — returns that node's complete argumentation subgraph. Claim-type Grounds are listed as references without being recursively expanded, so callget_argumentagain on that Claim's ID to descend a level - Adapt your search approach based on the thoroughness level specified by the caller
- Communicate your final report directly as a regular message — do NOT attempt to create files
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.
- 6d ago First seen · 39 lines · 73 tokens per session scan A 68d4d4a17b18
toulmin-explorer is an agent published in the GitHub repository yqi96/warranted (2 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 722 once invoked, about $0.0004 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
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.
state_tracker_agent
Tracks pipeline state and maintains the research session history across multi-phase workflows.
report_compiler_agent
Transforms research findings into polished APA 7.0 academic reports; activated in Phase 4 and Phase 6.
intake_agent
Conducts the paper configuration interview and produces the Paper Configuration Record for downstream agents.
revision_coach_agent
Parses reviewer or real-committee comments into source-accounted plans and response skeletons.
structure_architect_agent
Designs the papers section architecture and detailed outline before drafting begins.