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/traverse-framework/traverse/traverse-opsnpx skills add traverse-framework/traverse --skill traverse-opsgit clone --depth 1 https://github.com/traverse-framework/traverseWhat 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.00063 | $0.01502 |
| Opus 5 | $0.00032 | $0.00751 |
| Sonnet 5 | $0.00013 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
traverse-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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traverse Ops
Use this skill when the user wants Codex to start or resume the standard Traverse operating model.
Canonical trigger:
TRAVERSE OPS
Workflow
- Read
AGENTS.mdand follow the agent coordination rules. - Read the constitution (via
traverse-framework/.github, pinned in.governance-version) only when the ticket touches architecture, contracts, or versioned surfaces — lazy-read map in the org'sdocs/ai-agent-hardening.md. - Inspect current GitHub and Project 1 state.
- Prefer finishing existing open PRs before claiming new Ready work.
- Keep cycling through open PRs and Ready Project 1 issues until no actionable Ready tickets remain. Do not stop after one PR, one issue, or one merge.
- If no active PR needs attention, pick the next Ready Project 1 issue.
- Before work on an issue, run the Claude pre-flight checks from
AGENTS.md:- issue must not have
agent:claude - no remote
claude/issue-NNN-*branch may exist
- issue must not have
- If pre-flight passes, claim the issue:
- add
agent:codex - set Project 1
StatustoIn Progress
- add
- Use a dedicated
codex/issue-NNN-*branch. - Keep work scoped to the claimed issue and governing spec.
- Open a dedicated PR using the org body superset (
## Summary,## Governing Spec,## Project Item,## Definition of Done,## Validation) with validation evidence, then immediately queue it:gh pr merge <N> --squash --auto. Do not poll checks — continue the loop and release on a later pass once merged. This repo requires branches up to date withmain(strict checks): rebase when behind, or auto-merge cannot fire. - The stop condition is strict: no mergeable or fixable open PRs, no Ready
Project 1 tickets that pass pre-flight, no uncompleted
agent:codextickets, and only explicitly blocked work remains. If a Ready ticket is blocked, update its ticket/Project state with the concrete blocker before continuing to the next Ready ticket.
Continuation Rule (mandatory)
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.
- 2d ago First seen · 122 lines · 63 tokens per session scan A 1e50d7cf7efe
traverse-ops is a skill published in the GitHub repository traverse-framework/traverse (93 stars, last pushed 2d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,502 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-08-30.
Other skills, from other repositories
superplane-issue-logger
When researching, classifying, drafting, or logging general SuperPlane issues (bug, enhancement, feature, papercut). Use for natural-language issue descriptions, tmp/pmlogger drafts, and optional GitHub MCP logging with labels.
asana-webhooks
Receive and verify Asana webhooks. Use when setting up Asana webhook handlers, implementing the X-Hook-Secret handshake, debugging X-Hook-Signature verification, or handling task, project, and story events like added, changed, removed, deleted, and undeleted.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.