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/automateyournetwork/netclaw/github-opsnpx skills add automateyournetwork/netclaw --skill github-opsgit 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/github-ops)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/github-ops"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/github-ops.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 | $0.00061 | $0.00501 |
| Opus 5 | $0.00030 | $0.00251 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
github-ops 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
GitHub Operations Skill
Available Capabilities
Repository Operations
- Search repositories, list branches, get file contents
- Create/update files, create branches
- Compare branches, list commits
Issues
- Create, list, search, update, and comment on issues
- Use issues to track network findings, audit results, and remediation tasks
Pull Requests
- Create PRs for config changes, list PRs, get PR details
- Review and merge PRs, add comments
Code Search
- Search across repositories for configuration patterns
- Find references to specific IPs, VLANs, ACLs in config repos
GitHub Actions
- List workflow runs, get workflow status
- Trigger workflows for automated testing
Workflow Patterns
Network Finding → GitHub Issue
When you discover a network problem (via pyATS, health check, etc.):
- Create a GitHub issue with the finding details
- Include device name, symptom, recommended fix
- Label appropriately (bug, security, performance)
- Reference the GAIT session ID for audit trail
Config Change → Pull Request
When a config change is approved:
- Create a branch from main
- Commit the new/updated config file
- Open a PR with change details and ServiceNow CR number
- Link the PR in the GAIT audit trail
Audit Report → Repository
After health checks or audits:
- Commit the report as a markdown file
- Organize by date:
reports/YYYY-MM-DD/ - Include raw data and AI analysis
Environment Variables
GITHUB_PERSONAL_ACCESS_TOKEN— GitHub PAT with repo access
Important Rules
- Never commit secrets, passwords, or API keys to repositories
- Always create a branch for changes — never push directly to main
- Include meaningful commit messages describing the network change
- Reference ServiceNow CR numbers in PR descriptions when applicable
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 · 64 lines · 61 tokens per session scan A 0380ecf8673d
github-ops is a skill published in the GitHub repository automateyournetwork/netclaw (650 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 501 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
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
issue-progress-tracking
GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or…
mk:ghpm
GitHub project management via the gh CLI — create and triage issues, manage GitHub Projects v2 boards (add items, update status fields), manage labels and milestones, and generate handoff-status summaries. Use when "create a GitHub issue", "add to project board", "update sprint status", "create label/milestone", or…
baron
Drive work tracking (issues) and source control (pull requests) through Baron's provider-agnostic ports. Use when the user asks to create/transition/comment/link/query issues, open branches or pull requests, or run a Baron recipe — across Azure DevOps, GitHub, or whatever the repo's .baron/policy.json binds.
github-manager
GitHub operations - manage issues, pull requests, repositories, and workflows via GitHub API.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.