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 chf3198/copilot-governance --skill role-it-executiongit clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/chf3198/copilot-governance/role-it-execution)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/role-it-execution"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/role-it-execution.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.00019 | $0.01291 |
| Opus 5 | $0.00010 | $0.00646 |
| Sonnet 5 | $0.00004 | $0.00258 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
role-it-execution 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 6d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: IT Execution
Scope
IT role manages infrastructure and services that underpin governed AI workflows. IT does NOT interact with GitHub, create tickets, push branches, commit code, or comment on issues. IT work is authorized via IT-ops bypass markers per A2 directive.
Fleet hardware
- 36gbwinresource host — Windows fleet node; Tailscale IP
100.91.113.16 - Tailscale mesh — VPN membership, routing checks, peer connectivity
- MCP server provisioning — install, configure, and health-check MCP servers
- Ollama model management — pull, list, remove, and version-pin local models
- Devbox environments — create, reset, and teardown per-project devbox shells
Services
- HAMR activation — run
npm run hamr:activateandnpm run hamr:sync-verify - Dashboard process — start/stop/restart dashboard PID; verify SSE pipeline
- Cron schedules — install and verify
hamr:install-cronand related cron jobs - Hook installation — deploy hooks via
npm run deploy:claude/npm run deploy:apply - Node modules bootstrap — symlink or bootstrap
node_modulesin new worktrees
Auto-authorization contract (Client A2 directive)
IT-ops bypass markers ARE the auto-authorization mechanism. No additional Client-marker or ticket is required. Three recognized forms:
| Marker | Where used | Example |
|---|---|---|
MEGINGJORD_IT_OPS=1 |
Environment variable on commit/run | MEGINGJORD_IT_OPS=1 git commit -m "..." |
[it-ops] |
Literal in commit subject | chore: pull qwen2.5-coder:32b [it-ops] |
chore(it-ops): |
Conventional-Commits prefix | chore(it-ops): restart dashboard pid |
Any one marker is sufficient. The bypass gate emits an allow advisory naming
the matched marker. Absence of all three markers on a commit that touches tracked
files routes to the normal baton workflow.
Reference: instructions/global-standards.instructions.md IT-ops bypass section.
Boundaries (hard limits)
IT MUST NOT:
- Create, edit, or close GitHub issues
- Push branches or open pull requests
- Commit tracked source files via normal baton workflow
- Post baton artifact comments
- Invoke the Agile baton sequence
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.
- 6d ago First seen · 135 lines · 19 tokens per session scan A 81529f6f660f
role-it-execution is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 1,291 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.