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 Quinoto-Tech/QuinotoSpec --skill quinotospec-mjolnir-refactorgit clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpecWrote 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/quinoto-tech/quinotospec/quinotospec-mjolnir-refactor)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-mjolnir-refactor"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-mjolnir-refactor/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/quinoto-tech/quinotospec/quinotospec-mjolnir-refactor"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-mjolnir-refactor.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.00035 | $0.01061 |
| Opus 5 | $0.00017 | $0.00531 |
| Sonnet 5 | $0.00007 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
quinotospec-mjolnir-refactor 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Mjolnir Refactor
Flujo para generar una Propuesta de Refactor "Mjolnir" que reescribe módulos enteros bajo demanda. Este workflow usa el sistema estándar de proposals de QuinotoSpec (.quinoto-spec/proposals/{slug}/) en lugar de una estructura paralela.
Datos requeridos para ejecutar el workflow
El workflow debe ser invocado con los siguientes datos. Si falta alguno, detener el proceso y solicitar al usuario antes de continuar.
- nombre: Nombre del módulo que se desea refactorizar. Se usa como slug de la propuesta (kebab-case).
- problema: Descripción del motivo por el que se desea refactorizar el módulo.
- resultado_esperado: Qué resultado se espera alcanzar a través de la refactorización.
- detalles_adicionales: Otras informaciones de valor (librerías, formatos, tecnologías, restricciones, etc.).
Paso 1 — Inicialización del contexto
Genera el archivo .quinoto-spec/proposals/{SLUG}/mjolnir-refactor.yml con el siguiente schema exacto:
nombre: ""
problema: ""
resultado_esperado: ""
detalles_adicionales: ""
ultimo_paso_completado: 0
Completa los campos con los datos provistos. El campo ultimo_paso_completado se usará para reanudar el flujo si falla en algún punto.
⚠️ Verificación humana requerida: Solicitar confirmación del usuario antes de continuar al paso 2. El usuario puede editar el
.ymlantes de aprobar.
Una vez confirmado, ejecuta quinotospec-update-changelog:
- Título: Mjolnir Init: {nombre}
- Resumen: Archivo de contexto generado en
.quinoto-spec/{nombre}/mjolnir-refactor.yml.
Paso 2 — Discovery del módulo + Mapa de Impacto
Actualiza
ultimo_paso_completado: 1en el.ymlal iniciar este paso. Si falla, el proceso puede reanudarse desde aquí.
- Mapa de impacto previo al discovery: Antes de analizar el módulo, identificar qué otros módulos, archivos o servicios del proyecto importan o dependen del módulo a refactorizar. Documentar este mapa en
.quinoto-spec/proposals/{SLUG}/00-impact-map.md. - Realiza un discovery completo del módulo actual usando como contexto los archivos de
.quinoto-spec/proposals/{SLUG}/. - El discovery debe incluir la definición de DoR/DoD específica para este refactor (no dejar
08-product-and-agreements.mdvacío).
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 · 85 lines · 35 tokens per session scan A 4535776e3a33
quinotospec-mjolnir-refactor is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,061 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-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…