A plugin that searches SpecStory coding histories from tools such as Claude Code, Codex, Cursor, and Gemini, then builds a lasting collection of past workflows. It can identify repeatable workflows and turn selected ones into skills for coding agents.

Use it to search coding history, compare repeated workflows, gather evidence about their outcomes, and create reusable agent skills from chosen practices.

It helps recover useful practices from previous coding sessions instead of leaving them buried in old conversation records.

lore — Plugin by specstoryai

Install

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.

Claude Code

/plugin marketplace add specstoryai/getspecstory

agentmods

npx agentmods add plugins/specstoryai/getspecstory/lore

Clone the repo

git clone --depth 1 https://github.com/specstoryai/getspecstory

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

lore 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 yesterday.

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.

lore/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "lore",
  "displayName": "SpecStory Lore",
  "version": "3.9.0",
  "description": "Mine your SpecStory coding histories (Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence and outcome labels, and forge the ones you choose into skills installed across every agent harness.",
  "author": {
    "name": "SpecStory",
    "url": "https://github.com/specstoryai"
  },
  "homepage": "https://github.com/specstoryai/getspecstory/tree/dev/lore",
  "repository": "https://github.com/specstoryai/getspecstory",
  "license": "Apache-2.0",
  "keywords": [
    "skills",
    "specstory",
    "mining",
    "agent-skills",
    "workflows",
    "lore"
  ]
}

Changes

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.

yesterday First seen · 22 lines scan A 0df6c94da17d

Subscribe to this mod's changes

lore is a plugin published in the GitHub repository specstoryai/getspecstory (1,316 stars, last pushed 7d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Research ai chat-history copilot copilot-chat vscode vscode-extension

lore

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

mcp-windbg

mcp-windbg

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins