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 agentmods add skills/projas01/sp-devcontrol/govern-changesnpx skills add PRojas01/SP-DevControl --skill govern-changesgit clone --depth 1 https://github.com/PRojas01/SP-DevControlWhat 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 | $0.00059 | $0.00395 |
| Opus 5 | $0.00030 | $0.00198 |
| Sonnet 5 | $0.00012 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
govern-changes 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 yesterday.
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
Gobernar cambios con DevControl
Usar las herramientas del MCP devcontrol para mantener un ciclo de desarrollo trazable y aprobado.
Flujo estándar
- Verificar el estado del proyecto con
devcontrol_status. - Si no hay sesión activa, iniciar una con
devcontrol_session_startindicando el objetivo. - Antes de cada cambio significativo, evaluar el riesgo con
devcontrol_policy_check(path o command). - Registrar cada cambio pendiente en la sesión activa.
- Aprobar o rechazar cambios con
devcontrol_approve_change/devcontrol_reject_changesegún la revisión. - Generar reporte de cumplimiento con
devcontrol_compliance_reportal finalizar.
Reglas
- Siempre pasar
projectRootexplícitamente para evitar ambigüedad entre proyectos. - Una sesión activa a la vez por proyecto.
- No aprobar cambios en paths protegidos sin justificación explícita.
- El reporte de compliance incluye sesiones, cambios, controles y riesgos acumulados.
Referencia de herramientas MCP
| Tool | Descripción |
|---|---|
devcontrol_status |
Estado: preflight, sesión activa, cambios pendientes |
devcontrol_session_start |
Iniciar nueva sesión de gobernanza |
devcontrol_approve_change |
Aprobar un cambio pendiente por ID |
devcontrol_reject_change |
Rechazar un cambio pendiente por ID |
devcontrol_policy_check |
Evaluar riesgo de path o command contra políticas |
devcontrol_compliance_report |
Generar reporte completo de cumplimiento |
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.
- yesterday First seen · 36 lines · 0 tokens per session scan A 5abf4ed09fac
govern-changes is a skill published in the GitHub repository PRojas01/SP-DevControl (0 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 395 once invoked, about $0.0003 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-31.
Other skills, from other repositories
unity-mcp-orchestrator
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for…
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
macos-test-triage
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…
comfyui
Use when working with ComfyUI workflows in OpenMontage, including comfyuiimage/comfyuivideo/comfyuimusic, custom workflowjson/workflowpath inputs, outputnode selection, missing model setup, LoRAs, low-VRAM workflow choices, and community workflow imports.