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-dependency-graphgit 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-dependency-graph)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-dependency-graph"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-dependency-graph/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-dependency-graph"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-dependency-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
- high Prompt Injection · line 64 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 68 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00030 | $0.00788 |
| Opus 5 | $0.00015 | $0.00394 |
| Sonnet 5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
quinotospec-dependency-graph 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Este workflow analiza cómo los servicios del sistema se comunican entre sí, detecta dependencias ocultas y alerta sobre contratos de API inconsistentes.
Precondición: Todos los sub-proyectos deben tener su */.quinoto-spec/discovery/ actualizado. Ejecutar quinotospec.stack-discovery si es necesario.
Paso 1 — Inventario de servicios
Escanea el root y lista todos los servicios con /.quinoto-spec/discovery/. Para cada uno, extrae de 04-endpoints-and-openapi.md la lista de endpoints expuestos.
Paso 2 — Detección de dependencias inter-servicio
Para cada servicio, analiza el código fuente buscando llamadas HTTP a otros servicios internos (fetch, axios, requests, httpx, etc.) o referencias a variables de entorno que apunten a URLs internas (ej. API_URL, SERVICE_HOST).
Construye la tabla de dependencias:
| Servicio Consumidor | Servicio Proveedor | Endpoint Consumido | Método | Hallado en |
|---|---|---|---|---|
| [servicio-a] | [servicio-b] | /api/users/{id} |
GET | src/services/user.service.ts |
Paso 3 — Contract Drift Detection
Para cada dependencia identificada en el paso anterior:
- Busca el endpoint consumido en el
04-endpoints-and-openapi.mddel servicio proveedor. - Compara el contrato esperado (método, parámetros, respuesta) contra lo que el consumidor asume.
- Si hay discrepancia → marcar como
⚠️ CONTRACT DRIFT.
Tabla de resultados:
| Consumidor | Proveedor | Endpoint | Estado | Detalle |
|---|---|---|---|---|
| servicio-a | servicio-b | GET /users/{id} |
✅ OK | Contratos alineados |
| servicio-c | servicio-b | POST /orders |
⚠️ DRIFT | Consumidor envía user_id, proveedor espera userId |
Paso 4 — Recursos y dependencias compartidas
Identifica recursos compartidos entre servicios:
- Bases de datos: ¿Más de un servicio escribe al mismo esquema/tabla?
- Sistemas de auth: ¿Qué servicios comparten el mismo JWT/token provider?
- Message brokers / queues: ¿Qué servicios publican/consumen de los mismos topics?
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 · 87 lines · 30 tokens per session scan A af883d2a52b5
quinotospec-dependency-graph is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 788 once invoked, about $0.0002 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 skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
platform-apex-anonymous-run
Use this skill to run anonymous Apex against the connected Salesforce org — from a .apex file or a pasted snippet — capturing the debug log, surfacing compile and runtime errors, and summarizing results. Trigger on phrases like "run this anonymous apex", "execute this script against my org", "run this snippet of…