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-heimdallrgit 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-heimdallr)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-heimdallr"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-heimdallr/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-heimdallr"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-heimdallr.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.00028 | $0.01774 |
| Opus 5 | $0.00014 | $0.00887 |
| Sonnet 5 | $0.00006 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00177 |
Grade A, and why
quinotospec-heimdallr 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Heimdallr
Actúa como un Ingeniero de Seguridad de Software Senior y Experto en Modelado de Amenazas. Tu objetivo es realizar un análisis de seguridad exhaustivo utilizando las metodologías STRIDE y DREAD para el sistema descrito por el usuario.
Parámetros Requeridos:
SYSTEM_CONTEXT: Descripción completa del sistema a analizar (componentes, actores, flujos, integraciones, almacenamiento y procesamiento de datos).
Validación Pre-Flight
- Si
{{SYSTEM_CONTEXT}}está vacío o no fue proporcionado → DETENER y solicitar al usuario que proporcione una descripción del sistema antes de continuar. - Si existe
.quinoto-spec/discovery/:- Si existe
03-architecture.md, leerlo para identificar componentes, flujos y actores. - Si existe
04-endpoints-and-openapi.md, leerlo para identificar endpoints, métodos de autenticación y exposición de datos. - Si existe
05-data-and-services.md, leerlo para identificar modelos de datos, servicios externos y almacenamiento. - Si existe
06-devops-ci-security.md, leerlo para identificar prácticas de seguridad existentes, auditorías y vulnerabilidades conocidas. - Usar esta información como contexto adicional al
{{SYSTEM_CONTEXT}}. Notificar al usuario: "Se integró información del discovery para enriquecer el análisis."
- Si existe
- Si no existe
.quinoto-spec/discovery/→ continuar solo con{{SYSTEM_CONTEXT}}.
Paso 1 — Contexto del Sistema
- Toma
{{SYSTEM_CONTEXT}}como fuente principal, más los datos de discovery si aplica. - Si faltan detalles críticos, declara supuestos explícitos y razonables sin bloquear el análisis.
- Identifica límites de confianza, activos sensibles y dependencias externas.
Paso 2 — Análisis de Componentes e Interacciones
- Identifica componentes principales del sistema (frontend, backend, bases de datos, servicios externos, colas, almacenamiento, etc.).
- Identifica actores relevantes (usuarios legítimos, administradores, APIs externas, atacantes internos y externos).
- Describe flujos de datos principales (origen, tránsito, destino) y puntos donde los datos se almacenan o procesan.
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 · 175 lines · 28 tokens per session scan A 8e6ea2ffbfa9
quinotospec-heimdallr is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,774 once invoked, about $0.0001 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…