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-ticket-contextgit 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-ticket-context)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/halo-ticket-context"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/halo-ticket-context/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-ticket-context"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/halo-ticket-context.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.00065 | $0.01645 |
| Opus 5 | $0.00032 | $0.00822 |
| Sonnet 5 | $0.00013 | $0.00329 |
| Haiku 4.5 | $0.00006 | $0.00164 |
Grade A, and why
halo-ticket-context 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Halo Ticket Context
Review a ticket in Halo to gather everything needed to understand and resolve it — the ticket detail, its full action/note history, the assets it touches, and related knowledge-base runbooks. Entirely read-only. Halo is HaloPSA / HaloITSM (the same product and REST API); tickets are called "Faults" in Halo's API vocabulary.
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 - Python: 3.10+ · Dependencies:
fastmcp,httpx,python-dotenv - Read/write posture: The whole server is read-only except one gated write (
halo_create_change_request, in the halo-change-request skill). Every tool in this skill is read-only.
Available Tools
| Tool | Parameters | What It Does |
|---|---|---|
halo_get_ticket |
ticket (numeric id) |
Read one ticket ("Fault") — summary, details, status, priority, client/site/user, and linked assets |
halo_get_ticket_actions |
ticket (numeric id) |
The ticket's actions/notes history (the investigation timeline) |
halo_list_tickets |
ticket_type?, customer?, asset_id?, status?, open_only?, search? |
Find a ticket by type, customer, asset, status, or free text |
halo_get_asset |
asset (name / inventory-number / id) |
Read a linked asset surfaced on the ticket |
halo_list_kb_articles |
search? |
Search the Halo knowledge base for related runbooks |
halo_get_kb_article |
article (numeric id) |
Read one KB article, including its body |
Key Concepts
- Halo == HaloPSA == HaloITSM. Same API for both editions.
- Tickets are "Faults" and are addressed by numeric id only — they are not name-resolvable. If you don't have the id, find it with
halo_list_tickets(bycustomer,asset_id,status, orsearch) first. - The Halo "Client" is the customer. Filter ticket lists to an org with the
customerparam (a client name or id). - Actions are the story.
halo_get_ticket_actionsreturns the note/action timeline — the richest source of what has already been tried and what remains. - Assets link tickets to devices.
halo_get_ticketreturns linked assets; read them withhalo_get_asset(or pivot to the halo-asset-context skill). - KB articles are the runbooks. Search with
halo_list_kb_articles, then read the full body withhalo_get_kb_articlefor resolution/runbook context. - Read-only. Nothing here writes. If a change is warranted, hand off to halo-change-request.
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 · 110 lines · 65 tokens per session scan A 2b943ce4925b
halo-ticket-context is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,645 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.