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 Spark-To-Paper-Skills/spark-to-paper-skills --skill ts-idea2storygit clone --depth 1 https://github.com/Spark-To-Paper-Skills/spark-to-paper-skillsWrote 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/spark-to-paper-skills/spark-to-paper-skills/ts-idea2story)<a href="https://agentmods.dev/skills/spark-to-paper-skills/spark-to-paper-skills/ts-idea2story"><img src="https://agentmods.dev/badge/skills/spark-to-paper-skills/spark-to-paper-skills/ts-idea2story/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/spark-to-paper-skills/spark-to-paper-skills/ts-idea2story"><img src="https://agentmods.dev/badge/skills/spark-to-paper-skills/spark-to-paper-skills/ts-idea2story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00141 | $0.02492 |
| Opus 5 | $0.00071 | $0.01246 |
| Sonnet 5 | $0.00028 | $0.00498 |
| Haiku 4.5 | $0.00014 | $0.00249 |
Grade A, and why
ts-idea2story 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 12d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ts-idea2story — idea → grounded research story (the upstream of ts-paper)
Distilled from the product's idea→story link. The idea is the PROTAGONIST; a recalled/searched
pattern is the TOOL it wields. Claude is the packager, the recaller, the searcher, the storyteller,
and the critic — all in one context (so coherence and anti-stacking come for free). Two scripts are
irreducible: kg_recall.py (vector/graph retrieval) and story_lint.py (the gate); embeddings
(optional) reuse ../ts-kg-build/scripts/embed.py's TS_EMBED_* config.
Inputs / Outputs
In: a raw idea (text); optional kg/ dir (from ts-kg-build, or the bundled kg_ts); optional
TS_EMBED_* endpoint; a retrieval_focus dial in {trust_kg, balanced, go_search_web}.
Out (in the workdir):
story.json— the 8 fields:title, abstract, problem_framing, gap_pattern, solution, method_skeleton, innovation_claims[], experiments_plan.story_proposal.md— the Markdown projection of the 8 fields (this is whatts-paper-planreads — a story IS a structured proposal; story2paper == proposal2paper).retrieved_papers.json— the real papers found, the citation seed forts-paper-cite(§ Reuse).logs/*.io.md, optionalnovelty_report.json.
Procedure
1. Package the idea (Claude)
Write idea_brief.json: motivation, problem, assumptions_explicit[], assumptions_inferred[], constraints, retrieval_query. Faithfulness guard: keep assumptions you inferred separate from
what the user stated — never fabricate user intent. The retrieval_query is an English,
search-friendly reformulation. Never raise on a thin idea; normalize and proceed.
2. Recall candidate patterns (script + Claude)
If a kg/ exists: python3 scripts/kg_recall.py --idea "<retrieval_query>" --kg <kg_dir> --out recall.json --topk 8.
It returns Top-K candidate patterns (semantic+graph if embeddings configured, else lexical-only,
labeled — treat lexical hits as weaker). Then YOU reason over them comparatively in one pass,
scoring each on three independent axes (no per-pattern round-trips needed):
- stability — reliable skeleton, well-trodden; novelty — differentiating, rare;
- domain_distance — how far the pattern's home domain is from the idea (sorted ASCENDING; a near-domain pattern transfers more safely, a far one is a riskier "storyteller" move). Size ≠ stability (a big cluster can be incoherent — check the pattern's coherence). If no KG: skip to search (or, with neither, generate the story from the idea alone — weakest, allowed).
What ships with it
5 files 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.
- 12d ago First seen · 137 lines · 141 tokens per session scan A 06244dee095b
ts-idea2story is a skill published in the GitHub repository Spark-To-Paper-Skills/spark-to-paper-skills (996 stars, last pushed 21d ago), licensed MIT. It adds 141 tokens to every session and 2,492 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…