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 bouob/sysadmin-skills --skill change-requestgit clone --depth 1 https://github.com/bouob/sysadmin-skillsWrote 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/bouob/sysadmin-skills/change-request)<a href="https://agentmods.dev/skills/bouob/sysadmin-skills/change-request"><img src="https://agentmods.dev/badge/skills/bouob/sysadmin-skills/change-request/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/bouob/sysadmin-skills/change-request"><img src="https://agentmods.dev/badge/skills/bouob/sysadmin-skills/change-request.svg" alt="Reviewed on agentmods" width="80" 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.00095 | $0.02246 |
| Opus 5.5 | $0.00038 | $0.00898 |
| Sonnet 5.5 | $0.00019 | $0.00449 |
| Haiku 4.5 | $0.00010 | $0.00225 |
Grade A, and why
change-request 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 1mo 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Request Workflow
Structured change management following ITIL 4 Change Enablement. Produces a complete RFC (Request for Change) document that serves as both the change plan and the CAB review submission.
Related Skills (auto-loaded)
- itil — change types (Standard/Normal/Emergency), CAB process, risk assessment matrix
- done-ops — verification gate before finalizing the change
Output
File: {OUTPUT_DIR}/change-request-{YYYY-MM-DD}-{slug}.md
- slug: lowercase kebab-case summary, e.g.
exchange-upgrade,ad-entra-migration - Change ID (
CHG-{YYYYMMDD}-{NNN}):{NNN}is a daily sequence number starting at 001. If the organization uses a ticketing system, use that system's ID instead.
Default output directory: ./changes/. If a docs/changes/ directory exists in the project, use that instead. Ask the user if neither exists. A user-specified path takes precedence over all defaults.
All change request documents are written in English. Before writing to file, preview the content for the user in their preferred language.
Workflow
Step 1: Gather Change Details
Collect the following from the user (use AskUserQuestion for missing items):
| Field | Required | Example |
|---|---|---|
| What is being changed? | Yes | "Upgrade Exchange Server 2019 to 2022" |
| Why is this change needed? | Yes | "End of support, security compliance" |
| Which systems/services affected? | Yes | "Email service, Active Directory" |
| Expected downtime? | Yes | "4-hour maintenance window" |
| Proposed schedule? | Yes | "Saturday 02:00-06:00" |
| Who will implement? | Yes | "IT Infrastructure team" |
Step 2: Classify the Change
Determine the change type using the itil skill:
| Question | Standard | Normal | Emergency |
|---|---|---|---|
| Is this a routine, pre-approved procedure? | Yes → Standard | No | No |
| Is there a documented SOP for this? | Yes → Standard | Maybe | No |
| Is this time-critical (active incident)? | No | No | Yes → Emergency |
| Otherwise | — | → Normal | — |
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.
- 1mo ago First seen · 242 lines · 95 tokens per session scan A 374961aeef78
change-request is a skill published in the GitHub repository bouob/sysadmin-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 95 tokens to every session and 2,246 once invoked, about $0.0004 per session on Opus 5.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
servicenow-change-management
ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use…
pace-change
A change-management skill for handling changes to planned product work, such as adding, pausing, resuming, reprioritising, or modifying requirements.
pace-release
A release-management workflow for coordinating software versions from preparation through deployment and closure. A release is a planned delivery of changes to users or an environment.
pace-retro
An iteration review and measurement tool for examining project progress, delivery results, quality, defects, and related trends. An iteration is a fixed period of development work.
pace-sync
A skill that synchronizes development-planning records with GitHub Issues. GitHub Issues are task and discussion entries attached to a software project.
change-advisory-board-process
Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment.…