quinotospec-import

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

An importer that brings tasks, user stories, and proposals from CSV, JSON, GitHub Issues, or an exported Jira CSV into `.quinoto-spec/`. GitHub Issues are work items tracked in a GitHub repository.

In plain words
What is it for?
Read local files or GitHub Issues, map common fields such as title, description, type, priority, status, and labels, and optionally preview the import without changing files.
Why use it?
It avoids re-entering existing work when moving planning data into the project's specification files.

Skill for Claude CodeCodex

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

Good fit Read local files or GitHub Issues, map common fields such as title, description, type, priority, status, and labels, and optionally preview the import without changing files.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-import"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-import.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,694 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.00026 $0.01694
Opus 5 $0.00013 $0.00847
Sonnet 5 $0.00005 $0.00339
Haiku 4.5 $0.00003 $0.00169

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

Security

Grade A, and why

quinotospec-import 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-import/SKILL.md · 170 lines

How it starts

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

Workflow: Import

Importa tareas, user stories y propuestas desde fuentes externas hacia .quinoto-spec/. Soporta import desde CSV, JSON, GitHub Issues (via gh CLI), y Jira CSV (export manual).

Precondiciones

  • El proyecto tiene .quinoto-spec/ inicializado
  • Existe al menos una propuesta activa (o se crea durante la import)
  • El archivo/source de import es accesible

Instrucciones

Paso 1 - Identificar Fuente de Import

Recibe parametros:

  • --source: Fuente de import (csv, json, github-issues, jira-csv)
  • --file: Ruta al archivo (para csv, json, jira-csv)
  • --repo: Repositorio GitHub (para github-issues, formato: owner/repo)
  • --proposal: Slug de propuesta destino (si no existe, se crea)
  • --prefix: Prefijo a usar para IDs generados (default: deriva del proposal)
  • --dry-run: Simular import sin hacer cambios

Paso 2 - Parsear Fuente

CSV/JSON:

  1. Lee el archivo
  2. Detecta columnas/campos automaticamente:
    • title / summary / name -> Titulo
    • description / body -> Descripcion
    • type / issue_type -> Tipo (epic, story, task)
    • priority -> Prioridad
    • status -> Estado
    • labels / tags -> Etiquetas
  3. Mapea columnas a campos QuinotoSpec
  4. Si no puede detectar, pide al usuario que mapee manualmente

GitHub Issues:

  1. Usa gh CLI para obtener issues del repositorio
  2. Filtra por labels si se especifica --label
  3. Convierte cada issue a tarea o user story segun labels:
    • Label "story" -> User Story
    • Label "epic" -> Propuesta
    • Sin label -> Tarea
  4. Preserva links a issues originales en metadata

Jira CSV:

  1. Parsea CSV exportado de Jira
  2. Mapea campos:
    • Summary -> Titulo
    • Description -> Descripcion
    • Issue Type -> Tipo (Epic -> Propuesta, Story -> US, Task/Sub-task -> Tarea)
    • Priority -> Prioridad
    • Status -> Estado (mapeo: To Do -> Pendiente, In Progress -> En Curso, Done -> Completada)
  3. Extrae Epic Link para asociar tareas a proposals

Read the full file on GitHub · 170 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 · 170 lines · 26 tokens per session scan A 1384c1a0e848

Subscribe to this mod's changes

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