What is quinotospec-mark-done?

A task-completion workflow for QuinotoSpec tracking files. It marks a named task complete and archives the task or user-story files when all related work is finished.

Use it after completing a technical task such as TSK-XXX to update its tracking file, archive finished task lists, and archive fully completed user stories.

It keeps task checkboxes, proposal records, and archived work consistent instead of leaving completed items in active files.

quinotospec-mark-done — Skill for Cursor by Quinoto-Tech/QuinotoSpec

Install

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.

Any agent

npx skills add Quinoto-Tech/QuinotoSpec --skill quinotospec-mark-done

Clone the repo

git clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpec

Made for: Cursor.

Or install quinotospec, the plugin that ships this one along with the rest of its 90 skills, 9 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-mark-done/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-mark-done)

Your own site

<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.

Your own site · 80×15

<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>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,563 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

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.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.01563
Opus 5.5	$0.00015	$0.00625
Sonnet 5.5	$0.00008	$0.00313
Haiku 4.5	$0.00004	$0.00156

Measured 1mo ago against content hash b82df7b4add0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

agent-dist/skills/quinotospec-mark-done/SKILL.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 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-MNEM-suffix-NNN) ha sido completada. Antes de modificar estados, ejecuta quinotospec-verify-before-done; después actualiza los archivos de seguimiento usando el contrato común y, si el elemento está 100% completo, lo mueve a _archived/.

Instrucciones de Ejecución

Modo Individual

Paso 0 — Verificar antes de modificar estados

Ejecuta quinotospec-verify-before-done con el TASK_ID y la evidencia de la tarea.
Valida .quinoto-spec/evidence/{{TASK_ID}}/verify-before-done.json con evidence_validate.py --kind verify-before-done --require --json.
Revisa cada criterio DoD, tests, lint, typecheck y el diff.
Si falta evidencia o una verificación falla, detén el proceso y mantén la tarea en in_progress o blocked.
Solo después de un gate exitoso continúa marcando el checkbox o moviendo archivos.

Paso 1 — Marcar la tarea como completada

Ejecuta python3 agent-dist/skills/quinotospec-contract/contract.py inspect --root . --json y localiza el canonical_id de la tarea.
Busca el archivo *_tasks.md que contenga el task ID; no asumas que el nombre del archivo contiene el story ID.
Si el ID no existe, notifica al usuario y detén el proceso.
Cambia la columna Estado de [ ] a [x] para esa tarea. En legacy, cambia el checkbox o etiqueta de estado equivalente.

Paso 2 — Verificar completitud del archivo de tareas

Consulta el contrato normalizado y cuenta tareas con status: pending, blocked o unknown.
Si todas las tareas de la story tienen status: completed:
1. Mueve el archivo a .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/_archived/{{TASKS_FILE}}.
2. Ve al Paso 3.
Si aún quedan tareas pendientes, ve directo al Paso 4.

Paso 3 — Verificar completitud de la User Story

Busca la story por el campo Historia Relacionada de las tareas, no por similitud numérica.
Si todas las tareas de esa story están completed y no quedan stories con tareas pendientes:
1. Mueve user-stories.md a .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/_archived/user-stories.md.
2. Actualiza el **Estado:** en proposal.md a ✅ Completada.
3. Ejecuta nuevamente el validador del contrato antes de archivar la propuesta completa.

Read the full file on GitHub · 121 lines

Changes

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.

1mo ago Changed · -6 lines b82df7b4add0
2mo ago First seen · 127 lines · 38 tokens per session scan A bcecd5cd8174

Subscribe to this mod's changes

quinotospec-mark-done is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,563 once invoked, about $0.0002 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.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens