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-extension-managergit 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-extension-manager)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-extension-manager"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-extension-manager/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-extension-manager"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-extension-manager.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00655 |
| Opus 5.5 | $0.00012 | $0.00262 |
| Sonnet 5.5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
quinotospec-extension-manager 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extension Manager
Gestiona el ciclo de vida de extensiones y presets sin ejecutar código remoto ni resolver conflictos silenciosamente.
Modelo
- Extensiones:
.quinoto-spec/extensions/<id>/extension.yml. - Presets:
.quinoto-spec/presets/<id>/preset.yml. - Registro auditable:
.quinoto-spec/extensions/.registry. - Catálogos locales:
extensions/catalog.jsonyextensions/catalog.community.json. - Resolución de templates:
quinotospec-template-resolveraplica overrides → presets → extensions → core.
Comandos
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . --json search jira
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . install --kind extension --source ./my-extension
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . update --kind extension --source ./my-extension
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . --json list
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . info --kind extension my-extension
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . remove --kind extension my-extension --yes
install y update validan el manifest antes de copiar, rechazan symlinks y escriben el registro atómicamente. remove exige --yes y solo elimina paths registrados.
Hooks
Los hooks se declaran en extension.yml bajo los 17 puntos del contrato. Listarlos es read-only:
python3 agent-dist/skills/quinotospec-extension-manager/extension_manager.py \
--root . --json hooks --point before_apply
Ejecutar hooks automáticos requiere --run --yes; los hooks manuales solo se reportan. Los comandos se ejecutan sin shell, con timeout y código de salida visible.
Seguridad
- No instalar fuentes HTTP por defecto; el catálogo debe entregar un path local verificable.
- No modificar el core para registrar una extensión.
- No ejecutar hooks
autoduranteinstalloupdate; hacerlo requiere una invocación explícita. - Rechazar IDs, paths, manifests y archivos fuente inseguros.
- Registrar el cambio con
quinotospec-update-changelogdespués de instalar, actualizar o remover.
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.
- 1mo ago First seen · 67 lines · 31 tokens per session scan A 19240c85bb01
quinotospec-extension-manager is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 655 once invoked, about $0.0001 per session on Opus 5.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-26.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…