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-importgit 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-import)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-import"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-import/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-import"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-import.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.00026 | $0.01694 |
| Opus 5 | $0.00013 | $0.00847 |
| Sonnet 5 | $0.00005 | $0.00339 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
quinotospec-import 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Import
Importa tareas, user stories y propuestas desde fuentes externas hacia .quinoto-spec/. Soporta import desde CSV, JSON, GitHub Issues (via gh CLI), y Jira CSV (export manual).
Precondiciones
- El proyecto tiene
.quinoto-spec/inicializado - Existe al menos una propuesta activa (o se crea durante la import)
- El archivo/source de import es accesible
Instrucciones
Paso 1 - Identificar Fuente de Import
Recibe parametros:
--source: Fuente de import (csv,json,github-issues,jira-csv)--file: Ruta al archivo (para csv, json, jira-csv)--repo: Repositorio GitHub (para github-issues, formato:owner/repo)--proposal: Slug de propuesta destino (si no existe, se crea)--prefix: Prefijo a usar para IDs generados (default: deriva del proposal)--dry-run: Simular import sin hacer cambios
Paso 2 - Parsear Fuente
CSV/JSON:
- Lee el archivo
- Detecta columnas/campos automaticamente:
title/summary/name-> Titulodescription/body-> Descripciontype/issue_type-> Tipo (epic, story, task)priority-> Prioridadstatus-> Estadolabels/tags-> Etiquetas
- Mapea columnas a campos QuinotoSpec
- Si no puede detectar, pide al usuario que mapee manualmente
GitHub Issues:
- Usa
ghCLI para obtener issues del repositorio - Filtra por labels si se especifica
--label - Convierte cada issue a tarea o user story segun labels:
- Label "story" -> User Story
- Label "epic" -> Propuesta
- Sin label -> Tarea
- Preserva links a issues originales en metadata
Jira CSV:
- Parsea CSV exportado de Jira
- Mapea campos:
Summary-> TituloDescription-> DescripcionIssue Type-> Tipo (Epic -> Propuesta, Story -> US, Task/Sub-task -> Tarea)Priority-> PrioridadStatus-> Estado (mapeo: To Do -> Pendiente, In Progress -> En Curso, Done -> Completada)
- Extrae
Epic Linkpara asociar tareas a proposals
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 · 170 lines · 26 tokens per session scan A 1384c1a0e848
quinotospec-import is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,694 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
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.