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 agentmods add skills/renzo-tognella/decisionssearch/create-code-pattern-memorynpx skills add Renzo-Tognella/DecisionsSearch --skill create-code-pattern-memorygit clone --depth 1 https://github.com/Renzo-Tognella/DecisionsSearchWhat 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 | $0.00100 | $0.02236 |
| Opus 5 | $0.00050 | $0.01118 |
| Sonnet 5 | $0.00020 | $0.00447 |
| Haiku 4.5 | $0.00010 | $0.00224 |
Grade A, and why
create-code-pattern-memory 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Code Pattern Memory
Você captura padrões de implementação que podem ser repetidos com segurança em outros lugares. Um CodePattern não é sinônimo de código bem escrito, convenção presumida ou ocorrência única: precisa de evidência explícita de que deve ser reutilizado.
CORE RULE: Compare com code-patterns.md e exija evidência explícita de reuso ou padronização antes de criar. Nunca persista sem preview e confirmação.
When to activate
- Trigger phrases: "registra esse padrão de código", "documenta essa convenção", "isso virou padrão, captura"
- Contexts: PR ou revisão diz explicitamente que algo deve ser repetido; o mesmo idiom aparece em múltiplos arquivos/locais independentes; a triagem da decisionssearch-capture encontra uma convenção formalizada
Do NOT activate for:
- uma implementação one-off, mesmo que pareça elegante → mantenha em create-pr-memory/FeatureDescription
- escolha de tecnologia/design com trade-off → use create-architectural-decision-memory
- verdade de domínio/produto → use create-business-rule-memory
- "por que esse arquivo é assim?" → use code-blame
Inputs
- pattern_source (required): PR, diff, código, revisão ou item do digest. Fonte: fontes indicadas|digest|Git.
- mode (optional, default: standalone): standalone | orchestrated.
session_review(required emstandalone): escolha explícita entreentire_current_sessioneindicated_sources_only; é metadado de preview, não campo dememory.manual.create.
Evidência mínima obrigatória
Aceite somente se houver pelo menos uma das bases abaixo:
- Padronização explícita: PR, review, guideline ou autor diz que a estrutura/idiom deve ser usado, repetido ou adotado como padrão.
- Repetição verificável: o mesmo padrão aparece em pelo menos dois arquivos ou locais independentes, com referências concretas.
- Regra de replicação: existe instrução operacional clara para aplicar o padrão em novas implementações, acompanhada de exemplos.
Similaridade visual, preferência do agente, um único arquivo, um único PR ou uma abstração local não bastam. Sem essa evidência, não crie CodePattern; capture o fato como PRMemory e, se necessário, encaminhe para BusinessRule ou ArchitecturalDecision.
What ships with it
1 file 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.
- yesterday First seen · 150 lines · 100 tokens per session scan A 914adf875cd7
create-code-pattern-memory is a skill published in the GitHub repository Renzo-Tognella/DecisionsSearch (0 stars, last pushed 8d ago), licensed MIT. It adds 100 tokens to every session and 2,236 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.