What is quinotospec-archive?

A workflow for moving completed technical proposals, user stories, or task files into an archive. Archiving removes finished planning material from the active workspace while keeping a record of it.

Use it to archive a finished proposal, a proposal’s user stories, or a specific completed task file after checking its status and documenting a summary.

It keeps the working area easier to navigate and checks that the selected work is actually complete before moving it.

quinotospec-archive — Skill for Claude Code and Codex by Quinoto-Tech

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

Clone the repo

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

Made for: Claude Code, Codex.

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-archive/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-archive)

Your own site

<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-archive"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-archive/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-archive"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,177 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.

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.00016	$0.01177
Opus 5	$0.00008	$0.00589
Sonnet 5	$0.00003	$0.00235
Haiku 4.5	$0.00002	$0.00118

Measured 12d ago against content hash 12a47ccdf6f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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

agent-dist/skills/quinotospec-archive/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow: Archive

Este workflow permite archivar elementos de la especificación técnica que han sido completados para limpiar el espacio de trabajo.

Objetivos:

Propuesta completa: Archiva la carpeta entera de una propuesta.
User Stories: Archiva el archivo user-stories.md de una propuesta.
Tareas: Archiva un archivo de tareas específico (ej. US-XXX-001_tasks.md).

Elemento a archivar: {{TARGET}} (puede ser un slug de propuesta, un archivo específico o un patrón)

Instrucciones de Ejecución:

Validación previa (OBLIGATORIA):
- Lee proposal.md y verifica que el **Estado:** sea ✅ Completada o equivalente a Done.
- Si quedan user stories o tareas sin completar ([ ] en los archivos de tareas), advierte al usuario y detén el proceso a menos que confirme explícitamente continuar.
- Genera un resumen rápido: cuántas historias y tareas contenía el elemento, cuántas fueron completadas vs pendientes. Documenta esto en el changelog.
Merge de Delta Specs (solo si la propuesta tiene delta-specs/):

Si el target es una propuesta y existe el directorio delta-specs/ dentro de ella:
1. Por cada dominio en delta-specs/:
  - Determinar archivo target: .quinoto-spec/specs/{{dominio}}/spec.md
  - Si NO existe el archivo target:
    - Crear directorio .quinoto-spec/specs/{{dominio}}/
    - Crear spec.md con header # Spec: {{dominio}} y seccion ## Current Requirements
2. Procesar ADDED Requirements:
  - Leer cada ### Requirement: {{name}} de la seccion ADDED Requirements en delta-specs/{{dominio}}/spec.md
  - Para cada uno, append al final de .quinoto-spec/specs/{{dominio}}/spec.md con separador --- antes del bloque
3. Procesar MODIFIED Requirements:
  - Leer cada ### Requirement: {{name}} de la seccion MODIFIED Requirements
  - Buscar el bloque ### Requirement: {{name}} en el spec target (match por nombre exacto)
  - Si se encuentra: reemplazar el bloque completo (desde ### Requirement: hasta el siguiente ### o --- o EOF)
  - Si NO se encuentra: advertir ⚠️ Requirement '{{name}}' no encontrado en specs/{{dominio}}/spec.md. ¿Agregar como ADDED?

Read the full file on GitHub · 78 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.

12d ago First seen · 78 lines · 16 tokens per session scan A 12a47ccdf6f6

Subscribe to this mod's changes

quinotospec-archive is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,177 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.

Planning Project management

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

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…

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

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

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.

apache/magpie · 73 tokens