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 gait-session-trackinggit 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/gait-session-tracking)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/gait-session-tracking"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gait-session-tracking/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/gait-session-tracking"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gait-session-tracking.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.00062 | $0.02566 |
| Opus 5.5 | $0.00025 | $0.01026 |
| Sonnet 5.5 | $0.00012 | $0.00513 |
| Haiku 4.5 | $0.00006 | $0.00257 |
Grade A, and why
gait-session-tracking 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 26d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GAIT Session Tracking
This skill is mandatory. Every NetClaw session MUST begin with gait_branch and end with gait_log.
How to Call the Tools
The GAIT MCP server provides the lifecycle tools below (discover tools/list for the complete installed inventory). Call them via mcp-call:
Check Repository Status
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_status '{}'
Returns current branch, uncommitted changes, and repository state.
Initialize a New GAIT Repository
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_init '{"path":"/absolute/path/to/project"}'
Creates a new GAIT repository if one does not already exist. Supply the actual absolute project path; do not run against the filesystem root. Run once during initial setup, then verify gait_status names the intended root.
Create a New Branch (SESSION START)
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_branch '{"name":"health-check-r1-2026-02-21"}'
Creating a branch does not switch to it. Call gait_checkout with the same name and verify gait_status before recording turns. Every session begins here. Use a descriptive branch name that includes the action type, target device(s), and date. Examples:
health-check-r1-2026-02-21ospf-troubleshoot-core-2026-02-21config-deploy-acl-update-2026-02-21netbox-reconcile-site-hq-2026-02-21security-audit-dmz-2026-02-21
Switch to an Existing Branch
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_checkout '{"name":"health-check-r1-2026-02-21"}'
Use this to resume a previous session or switch context between parallel investigations.
Record an AI Turn (PRIMARY RECORDING TOOL)
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_record_turn '{"user_text":"User asked to check CPU on R1","assistant_text":"Ran show processes cpu sorted. CPU 5-min avg: 12%. Status: HEALTHY.","artifacts":[{"path":"show_proc_cpu_r1.txt","content":"Sanitized evidence reference; raw evidence retained locally."}]}'
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.
- 26d ago Changed · +4 lines 4bd71904d154
- 1mo ago Changed · +6 lines 59422a817c8c
- 1mo ago First seen · 183 lines · 62 tokens per session scan A 35f58860bf7b
gait-session-tracking is a skill published in the GitHub repository automateyournetwork/netclaw (683 stars, last pushed 5d ago), licensed Apache-2.0. It adds 62 tokens to every session and 2,566 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
deliver-spec
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.