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-specs-initgit 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-specs-init)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-specs-init"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-specs-init/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-specs-init"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-specs-init.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.00019 | $0.01439 |
| Opus 5 | $0.00010 | $0.00720 |
| Sonnet 5 | $0.00004 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade C, and why
quinotospec-specs-init scanned grade C with 1 finding 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 9d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Requerimientos actuales del sistema para el dominio {{dominio}}. Formato: ### Requirement: Name The system SHALL/MUST/SHOULD ... #### Scenario: Name (optional) - GIVEN precondition - WHEN action - THEN expected outc How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Specs Init
Inicializa el directorio specs/ con requerimientos extraidos del discovery o de propuestas activas. Util para proyectos que ya usaban QuinotoSpec antes de delta-specs, o para crear la base inicial de specs desde cero.
Modos
| Modo | Flag | Fuente |
|---|---|---|
| Desde Discovery | --from-discovery |
.quinoto-spec/discovery/ (03-architecture, 05-data-and-services, 04-endpoints) |
| Desde Propuestas | --from-proposals |
.quinoto-spec/proposals/*/proposal.md activas |
| Desde Cero | (default) | 01-stack-profile.md para estructura de dominios |
Paso 1 — Verificar Estado
- Verificar si
.quinoto-spec/specs/ya tiene archivos.md(no solo README.md). - Si tiene archivos:
- Mostrar:
specs/ ya contiene {{N}} archivos en {{M}} dominios. - Advertir que la operacion puede sobrescribir contenido existente.
- Pedir confirmacion. Si el usuario no confirma, detener.
- Mostrar:
- Si no tiene archivos (solo README.md o vacio), continuar.
Paso 2 — Identificar Dominios
Segun el modo seleccionado:
Modo --from-discovery
- Leer
.quinoto-spec/discovery/03-architecture.md:- Extraer nombres de servicios/sub-proyectos mencionados.
- Buscar patrones:
**Servicio:**,**Componente:**,- servicio:, diagramas Mermaid.
- Leer
.quinoto-spec/discovery/05-data-and-services.md:- Extraer entidades y servicios externos.
- Agrupar entidades por dominio.
- Leer
.quinoto-spec/discovery/04-endpoints-and-openapi.md:- Extraer endpoints y agrupar por prefijo/dominio (ej.
/auth/*→ auth,/api/users/*→ users).
- Extraer endpoints y agrupar por prefijo/dominio (ej.
- Consolidar lista de dominios unicos.
Modo --from-proposals
- Leer todas las propuestas activas en
.quinoto-spec/proposals/*/proposal.md. - Extraer
**Servicios Afectados:**de cada propuesta. - Consolidar lista de dominios unicos.
- Para cada dominio, extraer requerimientos de la seccion
Especificacion Tecnica Detallada:- Parsear bloques de codigo, descripciones de endpoints, reglas de negocio.
- Convertir a formato
### Requirement: {{name}}. - Si hay informacion suficiente, agregar escenarios GIVEN/WHEN/THEN.
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.
- 9d ago First seen · 192 lines · 19 tokens per session scan C 56db6bf0ebc8
quinotospec-specs-init is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,439 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.