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-diffgit 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-diff)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-diff"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-diff/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-diff"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-diff.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.00024 | $0.00885 |
| Opus 5.5 | $0.00010 | $0.00354 |
| Sonnet 5.5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
quinotospec-diff 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: quinotospec-diff
Compara diferentes versiones de archivos QuinotoSpec para visualizar cambios a lo largo del tiempo. Util para entender la evolucion de una propuesta, detectar modificaciones no autorizadas o hacer audit trails.
Instrucciones de Ejecucion
Paso 1 - Identificar Objetivo de Comparacion
Recibe los siguientes parametros:
--file: Archivo a comparar (ruta relativa dentro de.quinoto-spec/)--proposal: Slug de propuesta (compara todos los archivos de la propuesta)--from: Version origen (fechaYYYY-MM-DDo tagv1,v2, etc.)--to: Version destino (fecha ocurrent) (default:current)--type: Tipo de diff (content,status,structure) (default:content)
Paso 2 - Obtener Versiones
- Para comparacion por fechas:
- Consulta
backup.py listybackup.py verifypara localizar un backup verificado de esa fecha - Si no hay backup verificado, usa git history:
git show HEAD@{YYYY-MM-DD}:path/to/file - Si el archivo no estaba versionado, reporta error
- Consulta
- Para comparacion por tags:
- Busca tags en git:
git show v1:path/to/file
- Busca tags en git:
- Para
current:- Lee el archivo actual del filesystem
Paso 3 - Generar Diff
Segun el --type:
- content: Diff linea por linea (formato unified diff)
- status: Solo cambios de estado (checkboxes, markers de completion)
- structure: Cambios en estructura (headings agregados/eliminados, secciones movidas)
Paso 4 - Formatear Output
Muestra el diff con:
- Lineas agregadas en verde (
+) - Lineas eliminadas en rojo (
-) - Lineas contextuales en gris
- Resumen al final: X agregadas, Y eliminadas, Z modificadas
Ejemplos
Diff de una Propuesta
/quinotospec-diff --proposal auth-jwt --from 2026-01-15
Diff de User Stories
/quinotospec-diff --file proposals/auth-jwt/user-stories.md --from 2026-01-15 --to current
Diff de Status (Solo Cambios de Completion)
/quinotospec-diff --proposal auth-jwt --type status --from 2026-01-01
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 Changed 1c96f09713df
- 2mo ago First seen · 85 lines · 24 tokens per session scan A c0122ad07b47
quinotospec-diff is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 885 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.