Borrowing it
Nothing to install: this file belongs to Quinoto-Tech/QuinotoSpec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Quinoto-Tech/QuinotoSpec/master/AGENTS.mdgit 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/instructions/quinoto-tech/quinotospec/agents-md)<a href="https://agentmods.dev/instructions/quinoto-tech/quinotospec/agents-md"><img src="https://agentmods.dev/badge/instructions/quinoto-tech/quinotospec/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.03028 | $0.03028 |
| Opus 5 | $0.01514 | $0.01514 |
| Sonnet 5 | $0.00606 | $0.00606 |
| Haiku 4.5 | $0.00303 | $0.00303 |
Grade A, and why
QuinotoSpec AGENTS.md 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 8d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guía para Agentes QuinotoSpec
Este es el paquete QuinotoSpec — una metodología y sistema de configuración de agentes para desarrollo asistido por IA. Los agentes operan en proyectos que usan QuinotoSpec siguiendo el flujo de trabajo "Proposal First" / "Context Slicing".
1. Comandos de Build, Lint y Test
Dado que este es un paquete de configuración de agentes (no una aplicación en tiempo de ejecución), los comandos tradicionales de build/test no aplican. Sin embargo, al trabajar en proyectos objetivo que usan QuinotoSpec:
Comandos de Análisis de Proyecto
# Detectar stack del proyecto
/quinotospec-stack-detect
# Ejecutar discovery completo
/quinotospec.discovery
# Validar estado del sistema antes de workflows críticos
/quinotospec-validate --full
Validación de Sintaxis
# Validar todos los archivos QuinotoSpec
/quinotospec-syntax-validate --type all
# Validar una propuesta específica
/quinotospec-syntax-validate --type proposal --slug <slug-name> --strict
Ejecutar Tests en Proyectos Objetivo
# Leer el perfil de stack para encontrar el comando de test correcto
cat .quinoto-spec/discovery/01-stack-profile.md
# Patrones comunes: npm test, pytest, bundle exec rspec, go test ./..., cargo test
Patrones para un solo test: npm test -- --testPathPattern=filename, pytest -k test_name, bundle exec rspec spec/path/to/spec.rb, go test -run TestName ./...
2. Convenciones de Código
Principios Fundamentales
- Proposal First: Siempre crear una propuesta técnica antes de escribir código
- Context Slicing: Discovery → Propuesta → User Stories → Tareas
- Nunca editar archivos de especificación manualmente: Usar skills como
quinotospec-update-changelog - Toda edición del agente debe registrarse: Después de cualquier cambio significativo, ejecutar
/quinotospec-update-changelogpara documentar la acción en el historial
Convenciones de Nombrado de Archivos
- Workflows:
quinotospec.<workflow-name>.md - Skills:
quinotospec-<skill-name>/SKILL.md - Rules:
quinotospec-rules.md - Scripts Temporales:
.quinoto-spec/scripts/temp_*.{py,sh,js}(NUNCA en raíz del proyecto)
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.
- 8d ago First seen · 261 lines · 3,028 tokens per session scan A 0c59eaaf45e7
QuinotoSpec AGENTS.md is an instructions file published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed 10d ago), licensed MIT. It adds 3,028 tokens to every session, about $0.0151 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.