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 automateyournetwork/netclaw --skill halo-change-requestgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/halo-change-request)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/halo-change-request"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/halo-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/automateyournetwork/netclaw/halo-change-request"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/halo-change-request.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.00066 | $0.03183 |
| Opus 5 | $0.00033 | $0.01591 |
| Sonnet 5 | $0.00013 | $0.00637 |
| Haiku 4.5 | $0.00007 | $0.00318 |
Grade A, and why
halo-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 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Halo Change Request
Open a change request in Halo through a strict discover -> preview -> confirm -> submit flow. Halo is HaloPSA / HaloITSM (the same product and the same REST API — HaloPSA is the MSP edition, HaloITSM the internal-IT edition). A "change request" in Halo is not a fixed object type: it is simply a ticket type ("Request Type") whose numeric id and custom fields are configured per organization — and an org often defines several change types (for example a customer-facing change and an internal change). This skill figures out which change is being raised, discovers the matching type, confirms it with a human, remembers it per category, learns its fields, and gates the single write behind explicit approval.
MCP Server
- Server:
halo-mcp(NetClaw-authored,mcp-servers/halo-mcp/) - Command:
python3 -u mcp-servers/halo-mcp/halo_mcp_server.py(stdio transport) - Auth: OAuth2 client-credentials —
HALO_CLIENT_ID/HALO_CLIENT_SECRETagainstHALO_BASE_URL(token from<base>/auth/token, resource API at<base>/api) - Python: 3.10+ · Dependencies:
fastmcp,httpx,python-dotenv - Read/write posture: read-only except one gated write —
halo_create_change_requestis the ONLY tool in the entire server that can mutate Halo, and it previews (no write) unlesssubmit=true.
This skill also uses the Memory MCP server (memory-mcp) to cache the confirmed change ticket type per Halo tenant.
Available Tools
| Tool | Parameters | What It Does |
|---|---|---|
halo_list_ticket_types |
can_create_only?, customer?, showcounts? |
Discover ticket types ("Request Types"). Use can_create_only=true to find the org's CHANGE type |
halo_get_ticket_type |
ticket_type |
Authoritative field schema for a type — required/optional/visible field definitions |
halo_list_fields |
custom_only? |
Master FieldInfo catalog (ids <-> names <-> dropdown option values) |
halo_get_field |
field |
One field definition by numeric id, with its lookup values |
halo_list_tickets |
ticket_type?, customer?, asset_id?, status?, open_only?, search? |
Find a sample existing change to copy field patterns from |
halo_get_ticket |
ticket (numeric id) |
Read one populated ticket as a concrete example |
halo_create_change_request |
summary, details, ticket_type, customer?, site?, user?, asset?, custom_fields?, submit=false |
THE ONLY WRITE. Previews the exact POST body unless submit=true |
halo_list_clients |
search? |
Resolve a Halo Client name to its id (the customer param) |
halo_list_sites |
customer?, search? |
Resolve a site within a client |
halo_list_users |
customer?, site_id?, search? |
Resolve the requesting contact/user |
memory_get_facts |
entity, key? |
Recall the tenant's change-type catalog (key="change_ticket_types") |
memory_record_fact |
entity, key, value, metadata? |
Merge a confirmed change type ({id, name, category}) into the catalog |
memory_record_decision |
context, decision, rationale, ... |
Log the human's ticket-type confirmation |
memory_invalidate |
fact_id, reason |
Retire a cached ticket type that no longer resolves |
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 · 177 lines · 66 tokens per session scan A 29dde4bb6090
halo-change-request is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 66 tokens to every session and 3,183 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.