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-mark-donegit 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-mark-done)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-mark-done"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-mark-done/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-mark-done"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-mark-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 95 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.
- high Tool Misuse · line 105 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.
- high Tool Misuse · line 117 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.00038 | $0.01362 |
| Opus 5 | $0.00019 | $0.00681 |
| Sonnet 5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
quinotospec-mark-done 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Mark Done
Usa esta skill cuando el usuario indica que una tarea técnica (TSK-XXX) ha sido completada. Actualiza los archivos de seguimiento y, si el elemento está 100% completo, lo mueve a _archived/.
Instrucciones de Ejecución
Modo Individual
Paso 1 — Marcar la tarea como completada
- Busca el
TSK-XXXdado en el archivo de tareas correspondiente.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/{{US_ID}}_tasks.md. - Si el ID no existe, notifica al usuario y detén el proceso.
- Cambia el checkbox
[ ]a[x]para esa tarea.
Paso 2 — Verificar completitud del archivo de tareas
- Cuenta los checkboxes
[ ]restantes en el archivo. - Si todas las tareas están completadas (
[x]):- Mueve el archivo a
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/_archived/{{US_ID}}_tasks.md. - Ve al Paso 3.
- Mueve el archivo a
- Si aún quedan tareas pendientes, ir directo al Paso 4.
Paso 3 — Verificar completitud de la User Story
- Busca el
{{US_ID}}correspondiente en.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.md. - Si todas las user stories de la propuesta están completadas:
- Mueve
user-stories.mda.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/_archived/user-stories.md. - Actualiza el
**Estado:**enproposal.mda✅ Completada.
- Mueve
Paso 4 — Registrar en el Changelog
Ejecuta la skill quinotospec-update-changelog con:
- Título de la Acción: Task Completed: {{TSK_ID}}
- Resumen: Se completó la tarea '{{TSK_ID}}' perteneciente a la historia '{{US_ID}}' en la propuesta '{{PROPOSAL_SLUG}}'.
Modo Bulk (Múltiples Tareas)
Usa --bulk o -b para marcar múltiples tareas a la vez:
/quinotospec-mark-done TSK-AUTH-001,TSK-AUTH-002,TSK-AUTH-003 --bulk
Paso 1 — Procesar lista de tareas
- Recibe array de IDs de tareas:
[TSK-AUTH-001, TSK-AUTH-002, ...] - Para cada ID:
- Busca y marca como completada
[x] - Acumula éxitos y errores
- Busca y marca como completada
Paso 2 — Verificar completitud por US
Después de procesar todas las tareas:
- Para cada US afectada, verificar si todas sus tareas están completas
- Si US completa, mover a
_archived/
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 · 127 lines · 38 tokens per session scan A bcecd5cd8174
quinotospec-mark-done is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,362 once invoked, about $0.0002 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.