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-schema-forkgit 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-schema-fork)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-schema-fork"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-schema-fork/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-schema-fork"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-schema-fork.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 107 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.00025 | $0.01208 |
| Opus 5 | $0.00013 | $0.00604 |
| Sonnet 5 | $0.00005 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
quinotospec-schema-fork 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 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.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Schema Fork
Permite crear una version personalizada del schema de artefactos (schema.yaml) adaptada al flujo de trabajo especifico del proyecto. Util cuando el schema default no se ajusta al proceso del equipo.
Modos
| Flag | Descripcion |
|---|---|
--from <schema> |
Schema base a forkear (default: quinotospec-default) |
--name <name> |
Nombre para el nuevo schema |
--add-artifact <id> |
Agrega un artefacto nuevo (pregunta interactiva) |
--remove-artifact <id> |
Elimina un artefacto del schema |
--skip-optional |
Omite artefactos marcados como opcionales |
--preview |
Muestra el schema resultante sin escribirlo |
Paso 1 — Cargar Schema Base
- Determinar schema fuente:
- Si
--from: buscar.quinoto-spec/schema.yaml(si existe) oagent-dist/templates/schema-template.yaml - Default:
agent-dist/templates/schema-template.yaml
- Si
- Parsear YAML y mostrar resumen:
Schema: quinotospec-default (v1) Artefactos: 7 Fases: 4 Reglas de validacion: 3
Paso 2 — Personalizar
Si se usa --add-artifact:
Preguntar interactivamente (una pregunta a la vez):
- ID del artefacto: Identificador unico (ej.
security-review) - Glob que genera: Path relativo a
.quinoto-spec/(ej.proposals/{slug}/security-review.md) - Dependencias: Lista de IDs de artefactos que deben existir antes (separados por coma)
- Template: Path a template (opcional, ej.
security-review-template.md) - Instruccion: Mini-prompt que el agente recibe
- Opcional: Si este artefacto es opcional (no bloquea dependientes)
- Fase: A que fase del ciclo pertenece (setup/planning/breakdown/implementation)
Si se usa --remove-artifact:
- Verificar que el artefacto exista en el schema.
- Advertir:
⚠️ Eliminar '{id}' puede romper dependencias. Artefactos afectados: {lista}. - Si se confirma, eliminar el artefacto y actualizar
requiresde los artefactos que dependian de el. - Si el artefacto eliminado era requerido por
apply.requires, advertir y pedir alternativa.
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 · 138 lines · 25 tokens per session scan A 8949074a8d95
quinotospec-schema-fork is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,208 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-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.