Borrowing it
Nothing to install: this file belongs to traverse-framework/traverse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/traverse-framework/traverse/main/.agents/skills/traverse-ops/SKILL.mdgit clone --depth 1 https://github.com/traverse-framework/traverseWrote 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/traverse-framework/traverse/traverse-ops)<a href="https://agentmods.dev/skills/traverse-framework/traverse/traverse-ops"><img src="https://agentmods.dev/badge/skills/traverse-framework/traverse/traverse-ops/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/traverse-framework/traverse/traverse-ops"><img src="https://agentmods.dev/badge/skills/traverse-framework/traverse/traverse-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 118 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00063 | $0.01502 |
| Opus 5.5 | $0.00025 | $0.00601 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (89 stars, last pushed 6d 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.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
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.