SpecStory is a local-first tool that records and indexes conversations with AI coding assistants so developers can search, reuse, and share their solutions. It is for preserving coding decisions, snippets, and other knowledge across projects and development tools. Its catalogue skills and commands process saved sessions into reusable agent skills and connect the workflow to coding agents.
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.
git clone --depth 1 https://github.com/specstoryai/getspecstoryWrote 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/commands/specstoryai/getspecstory/merge-conflict)<a href="https://agentmods.dev/commands/specstoryai/getspecstory/merge-conflict"><img src="https://agentmods.dev/badge/commands/specstoryai/getspecstory/merge-conflict/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/commands/specstoryai/getspecstory/merge-conflict"><img src="https://agentmods.dev/badge/commands/specstoryai/getspecstory/merge-conflict.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.00004 | $0.00153 |
| Opus 5 | $0.00002 | $0.00077 |
| Sonnet 5 | $0.00001 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
merge-conflict 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 11d 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.
What it actually says
Context
- Current git status: !
git status - Current git diff: !
git diff
Your task
Examine the current merge conflict using git commands.
Review each issue conflict by conflict and explain what caused each conflict. Explain what each side of the conflict was attempting to accomplish with their change.
Importantly, make a suggestion for the best resolution for each conflict, but only resolve them in discussion with me.
Use file names and line numbers to reference the changes, but also sequentially number every observation so we can easily reference them.
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.
- 11d ago First seen · 20 lines · 4 tokens per session scan A 4ce6f140a906
merge-conflict is a command published in the GitHub repository specstoryai/getspecstory (1,328 stars, last pushed 2d ago), licensed Apache-2.0. It adds 4 tokens to every session and 153 once invoked, about $0.0000 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-30.
Other commands, from other repositories
test-tools
Systematic smoke tests for Backseat Driver tools - validates core functionality and basic error handling after tool updates.
package
Look up library documentation using Context7 MCP tools for a specific task.
url
Scrape and integrate documentation from provided URLs using Firecrawl tools.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.
speckit.git.remote
Detect Git remote URL for GitHub integration.
apex-git-commit
Stage everything except agent-output/, infra/, and .github/skills/sensei/ (unless on feat/skills-sensei), auto-generate a conventional commit, push, then prompt to open or update a PR. CLI-only (git + gh).