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.
npx skills add Quinoto-Tech/QuinotoSpec --skill quinotospec-stack-detectgit 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/skills/quinoto-tech/quinotospec/quinotospec-stack-detect)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-stack-detect"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-stack-detect/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.
<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-stack-detect"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-stack-detect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00586 |
| Opus 5 | $0.00015 | $0.00293 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
quinotospec-stack-detect 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 9d 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.
What it actually says
Quinotospec Stack Detect
Esta skill permite al agente identificar automáticamente las tecnologías utilizadas en el proyecto.
Instrucciones de Análisis
Para detectar el stack técnico, busca y analiza los siguientes archivos en la raíz del proyecto:
1. Lenguajes y Frameworks Principales
- JavaScript/TypeScript:
package.json(Busca endependenciesydevDependencies). - Python:
requirements.txt,pyproject.toml,Pipfile,setup.py. - Go:
go.mod. - Rust:
Cargo.toml. - PHP:
composer.json. - Java/Kotlin:
pom.xml,build.gradle. - Ruby:
Gemfile.
2. Testing Frameworks
- Python:
pytest,unittest,tox. - JavaScript:
jest,vitest,mocha,cypress,playwright. - Go:
testing(estándar).
3. Herramientas de DevOps y CI/CD
- Docker:
Dockerfile,docker-compose.yml. - GitHub Actions:
.github/workflows/. - Husky/Lint-staged: Configuraciones en
package.json.
Formato de Salida Esperado
Genera un resumen en formato Markdown (será guardado en .quinoto-spec/discovery/01-stack-profile.md) con la siguiente estructura:
# 🛠️ Stack Profile: [Nombre del Proyecto]
**Discovery Date:** YYYY-MM-DD
## 🏗️ Core Technologies
- **Language:** [e.g. Python 3.10+]
- **Primary Framework:** [e.g. Django 4.2]
- **Package Manager:** [e.g. pipenv]
## 🧪 Quality & Testing
- **Test Runner:** [e.g. Pytest]
- **Linter/Formatter:** [e.g. Black, Flake8]
## 🚢 Infrastructure & DevOps
- **Containerization:** [e.g. Docker]
- **CI/CD:** [e.g. GitHub Actions]
## 📝 Coding Standards (Detected)
- [Ej: "Usa Service Layer", "Arquitectura Hexagonal", "Strict Typing"]
Ejemplo de Detección
Si se encuentra un package.json con "next": "14.x" y "vitest": "1.x", el perfil debe reflejar:
- Core: Next.js (React)
- Testing: Vitest
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.
- 9d ago First seen · 64 lines · 29 tokens per session scan A 914d062944e1
quinotospec-stack-detect is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 586 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…