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/luanpdd/kit-mcpWrote 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/luanpdd/kit-mcp/storytelling)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/storytelling"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/storytelling.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.00038 | $0.02011 |
| Opus 5 | $0.00019 | $0.01006 |
| Sonnet 5 | $0.00008 | $0.00402 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
storytelling 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 4d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cria/Atualiza:
.planning/storytelling/<module-slug>.md— relatório com story + inventário + CRC + hot spots
Após: o user reduz tempo de comprehension de codebase desconhecido de 4-8h (leitura cega manual) para 30 min (revisão informada de IA primeiro draft). Pré-requisito recomendado para /encontrar-seams ou /refactor-seguro em código novo.
Exemplos:
/storytelling src/orders/ # diretório completo
/storytelling src/orders/OrderService.ts # arquivo específico
/storytelling src/orders/ --depth=shallow # rápido — só story + inventário
/storytelling src/orders/ --include-tests # incluir tests no scope
/storytelling supabase/functions/process-payments/ # Edge Function module
Quando este comando é o caminho:
- Você herdou módulo desconhecido (onboarding, transferência, post-acquisition)
- Vai modificar código que não conhece
- Pré-requisito de
/encontrar-seamsou/refactor-seguro - Precisa identificar candidates de extract class antes de planejar refactor
- Code review onde reviewer não conhece o módulo
Quando NÃO é o caminho:
- Codebase < 200 linhas — leitura direta é mais rápida
- Você já trabalhou no módulo nas últimas 2 semanas — mental model fresco
- Mudança trivial (typo, comment) — overhead > valor
1. Parsear argumentos
TARGET=$(echo "$ARGUMENTS" | awk '{print $1}')
DEPTH=$(echo "$ARGUMENTS" | grep -oE -- '--depth[= ][^ ]+' | sed 's/--depth[= ]//')
MAX_LINES=$(echo "$ARGUMENTS" | grep -oE -- '--max-lines [0-9]+' | awk '{print $2}')
OUTPUT_PATH=$(echo "$ARGUMENTS" | grep -oE -- '--output [^ ]+' | awk '{print $2}')
INCLUDE_TESTS=false
echo "$ARGUMENTS" | grep -qE -- '--include-tests' && INCLUDE_TESTS=true
[ -z "$DEPTH" ] && DEPTH="deep"
[ -z "$MAX_LINES" ] && MAX_LINES=1500
if [ -z "$TARGET" ]; then
echo "ERROR: target obrigatório (arquivo ou diretório)"
exit 1
fi
if [ ! -e "$TARGET" ]; then
echo "ERROR: target não encontrado: $TARGET"
exit 1
fi
# auto-output path
if [ -z "$OUTPUT_PATH" ]; then
SLUG=$(basename "$(realpath "$TARGET")" | sed 's/[^a-zA-Z0-9]/-/g')
OUTPUT_PATH=".planning/storytelling/${SLUG}.md"
fi
mkdir -p "$(dirname "$OUTPUT_PATH")"
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.
- 4d ago First seen · 180 lines · 38 tokens per session scan A 62bfb30d79cc
storytelling is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 2,011 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-09-03.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.