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-pre-commitgit 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-pre-commit)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-pre-commit"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-pre-commit/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-pre-commit"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-pre-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 47 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00513 |
| Opus 5.5 | $0.00011 | $0.00205 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
quinotospec-pre-commit 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 2mo 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.
What it actually says
Workflow: Pre Commit
Objetivo: ejecutar una verificación pre-commit rápida antes de hacer push o crear un PR. No reemplaza CI completo, pero detecta problemas comunes antes de que lleguen al repo.
Instrucciones
Paso 1 - Ejecutar tests del stack
- Leer
.quinoto-spec/discovery/01-stack-profile.mdpara identificar el comando de test del proyecto. - Ejecutar el comando de test. Si falla, reportar los tests rotos y detener el workflow.
- Si no hay discovery o el comando de test no está definido, mostrar advertencia y continuar.
Paso 2 - Validar sintaxis QuinotoSpec
- Ejecutar
quinotospec-syntax-validate --type all. - Si hay errores de sintaxis, listarlos. No bloquear el commit, pero advertir.
Paso 3 - Enforce rules
- Ejecutar
quinotospec-rules-enforceen modowarning(nostrict). - Si se detectan violaciones de reglas, listarlas como advertencias.
Paso 4 - Resumen
Mostrar un resumen con el formato:
Pre-commit Check ─────────────────────────────
Tests: ✅ pasaron / ❌ fallaron / ⚠️ no configurados
Sintaxis: ✅ OK / ⚠️ {N} advertencias
Reglas: ✅ OK / ⚠️ {N} violaciones
──────────────────────────────────────────────
Si los tests fallaron, recomendar no hacer commit hasta que pasen. Si solo hay advertencias de sintaxis o reglas, el commit puede proceder.
Modos
- Default: Ejecuta los 3 pasos completos.
--quick: Solo ejecuta tests (saltea validación de sintaxis y reglas). Útil cuando los archivos QuinotoSpec no cambiaron.--skip-tests: Saltea tests del stack. Útil cuando solo se modificaron archivos de documentación o configuración.
Precondiciones
.quinoto-spec/discovery/debe existir (ejecutar@quinotospec.discoveryprimero).- Si no existe discovery, el workflow muestra advertencia y solo ejecuta validación de sintaxis + reglas.
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.
- 2mo ago First seen · 53 lines · 28 tokens per session scan A 3436fe0e9878
quinotospec-pre-commit is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 513 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.