quinotospec-export

quinotospec-export is a skill for Claude Code, Codex from Quinoto-Tech/QuinotoSpec. It costs 25 tokens per session (1,257 once invoked), scanned A, original, MIT.

A project-data exporter that reads proposals, tasks, and user stories from `.quinoto-spec/` and saves them as JSON, CSV, Markdown, or Jira-compatible CSV.

In plain words
What is it for?
Export all items or only proposals, tasks, or user stories, optionally limiting the export to one proposal and choosing the output file or directory.
Why use it?
It avoids copying project-planning information by hand when sharing it with tools such as Jira or GitHub Projects, or preparing reports.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Export all items or only proposals, tasks, or user stories, optionally limiting the export to one proposal and choosing the output file or directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/quinoto-tech/quinotospec/quinotospec-export
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-export
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.

agentmods badge for quinotospec-export

README.md
[![agentmods](https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-export/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-export)
Your own site
<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-export"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-export/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.

agentmods 80×15 button for quinotospec-export

Your own site · 80×15
<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-export"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-export.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,257 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 pass 7 Sept 2026
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.01257
Opus 5 $0.00013 $0.00629
Sonnet 5 $0.00005 $0.00251
Haiku 4.5 $0.00003 $0.00126

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

Security

Grade A, and why

quinotospec-export 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-export/SKILL.md · 148 lines

How it starts

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

Workflow: Export

Exporta datos de .quinoto-spec/ a formatos externos para integracion con herramientas de gestion de proyectos (Jira, GitHub Projects) o para reportes.

Precondiciones

  • El proyecto tiene .quinoto-spec/ con al menos una propuesta
  • Se tiene permisos de escritura en el directorio de salida

Instrucciones

Paso 1 - Determinar Alcance de Exportacion

Recibe parametros:

  • --proposal: Slug de propuesta especifica (default: todas)
  • --format: Formato de salida (json, csv, markdown, jira-csv) (default: json)
  • --output: Directorio o archivo de salida (default: .quinoto-spec/exports/)
  • --include: Que exportar (all, proposals, tasks, stories) (default: all)

Paso 2 - Recopilar Datos

Segun el alcance:

Propuestas:

  • Lee cada proposal.md en .quinoto-spec/proposals/*/
  • Extrae: slug, titulo, estado, fecha creacion, prefijo, descripcion, archivos afectados

User Stories:

  • Lee cada user-stories.md
  • Extrae: US_ID, titulo, descripcion, criterios de aceptacion, estado

Tareas:

  • Lee cada *_tasks.md
  • Extrae: TASK_ID, titulo, descripcion, estado, dependencias, criterios

Paso 3 - Transformar segun Formato

JSON:

{
  "export_date": "2026-04-15T10:30:00Z",
  "quinotospec_version": "2.0.0",
  "proposals": [
    {
      "slug": "auth-jwt",
      "title": "Implementar Auth JWT",
      "status": "En Curso",
      "prefix": "AUTH-a1b2",
      "created": "2026-04-01",
      "user_stories": [...],
      "tasks": [...]
    }
  ]
}

CSV:

type,id,title,status,proposal,description
proposal,auth-jwt,Implementar Auth JWT,En Curso,AUTH-a1b2,...
story,US-AUTH-001,Login endpoint,En Curso,auth-jwt,...
task,TSK-AUTH-001,Crear endpoint POST /login,Completada,auth-jwt,...

Jira CSV (para import en Jira):

Summary,Issue Type,Description,Priority,Status,Labels
"Implementar Auth JWT","Epic","...","High","In Progress","quinotospec,auth"
"Login endpoint","Story","...","High","In Progress","quinotospec,auth"
"Crear endpoint POST /login","Task","...","Medium","Done","quinotospec,auth"

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

  1. 12d ago First seen · 148 lines · 25 tokens per session scan A 18e0df5b5c2f

Subscribe to this mod's changes

quinotospec-export 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,257 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.

Related

Other skills, from other repositories

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