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 Biolytics-AI/rhetoric-engine --skill argument-spine-buildergit clone --depth 1 https://github.com/Biolytics-AI/rhetoric-engineWrote 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/biolytics-ai/rhetoric-engine/argument-spine-builder)<a href="https://agentmods.dev/skills/biolytics-ai/rhetoric-engine/argument-spine-builder"><img src="https://agentmods.dev/badge/skills/biolytics-ai/rhetoric-engine/argument-spine-builder/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/biolytics-ai/rhetoric-engine/argument-spine-builder"><img src="https://agentmods.dev/badge/skills/biolytics-ai/rhetoric-engine/argument-spine-builder.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.00040 | $0.00784 |
| Opus 5 | $0.00020 | $0.00392 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
argument-spine-builder 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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argument Spine Builder
Build a claim-evidence-warrant spine that makes the presentation answer-first. Prevent piles of facts, chronology, or topic lists that never make a claim.
Use after intent and insight are approved, and before slide thesis mapping.
Inputs
- Approved intent brief.
- Approved insight artifact, including labeled facts, inferences, assumptions, and open questions.
- Available evidence, source constraints, and required claims.
- Audience objections, decision criteria, and success test.
Outputs
Return an Argument Spine with:
core_claim: the answer the presentation asks the audience to accept.support_branches: main reasons that make the core claim believable and useful.warrants: why each support branch proves or advances the claim.evidence_needs: proof required, available evidence, gaps, and source priority.rebuttals: likely objections and the response strategy for each.
Use this compact format:
## Argument Spine
- Core claim:
- Support branches:
- Warrants:
- Evidence needs:
- Rebuttals:
- Approval questions:
Workflow
- State the answer first as a complete claim, not a topic or theme.
- Test the core claim against the intent brief: it must move the primary audience toward the desired change.
- Create three to five support branches, each phrased as a reason the claim is true, necessary, or preferable.
- For each branch, write the warrant: the reasoning bridge between evidence and claim.
- Attach available evidence only where it serves a branch. Do not dump facts without a claim job.
- Mark evidence needs as
available,needs source,needs user confirmation, oroptional backup. - Add rebuttals for objections that could block acceptance, action, trust, or timing.
- Order the spine by audience logic: what they need to accept first, not the order the user discovered it.
- Ask for approval before mapping slides.
Evaluation Checks
- The core claim answers the audience's implicit question.
- Each support branch is a claim-bearing reason, not a category label.
- Every evidence item has a job in the argument.
- Warrants are explicit enough to reveal weak logic.
- Rebuttals address real audience resistance, not straw objections.
- The spine can be summarized aloud in under one minute.
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.
- 8d ago First seen · 82 lines · 40 tokens per session scan A b52c55cbb4e9
argument-spine-builder is a skill published in the GitHub repository Biolytics-AI/rhetoric-engine (1 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 784 once invoked, about $0.0002 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 skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
lov-article-creator
A skill that turns source material or a draft into a complete, branded WeChat public-account article package.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…