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 chadixearth/graphyloop --skill terminal-opsgit clone --depth 1 https://github.com/chadixearth/graphyloopWrote 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/chadixearth/graphyloop/terminal-ops)<a href="https://agentmods.dev/skills/chadixearth/graphyloop/terminal-ops"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/terminal-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/chadixearth/graphyloop/terminal-ops"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/terminal-ops.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00046 | $0.00679 |
| Opus 5.5 | $0.00018 | $0.00272 |
| Sonnet 5.5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
terminal-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- terminal-ops — 95% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminal Ops
Use this when the user wants real repo execution: run commands, inspect git state, debug CI or builds, make a narrow fix, and report exactly what changed and what was verified.
This skill is intentionally narrower than general coding guidance. It is an operator workflow for evidence-first terminal execution.
Skill Stack
Pull these ECC-native skills into the workflow when relevant:
verification-loopfor exact proving steps after changestdd-workflowwhen the right fix needs regression coveragesecurity-reviewwhen secrets, auth, or external inputs are involvedgithub-opswhen the task depends on CI runs, PR state, or release statusknowledge-opswhen the verified outcome needs to be captured into durable project context
When to Use
- user says "fix", "debug", "run this", "check the repo", or "push it"
- the task depends on command output, git state, test results, or a verified local fix
- the answer must distinguish changed locally, verified locally, committed, and pushed
Guardrails
- inspect before editing
- stay read-only if the user asked for audit/review only
- prefer repo-local scripts and helpers over improvised ad hoc wrappers
- do not claim fixed until the proving command was rerun
- do not claim pushed unless the branch actually moved upstream
Workflow
1. Resolve the working surface
Settle:
- exact repo path
- branch
- local diff state
- requested mode:
- inspect
- fix
- verify
- push
2. Read the failing surface first
Before changing anything:
- inspect the error
- inspect the file or test
- inspect git state
- use any already-supplied logs or context before re-reading blindly
3. Keep the fix narrow
Solve one dominant failure at a time:
- use the smallest useful proving command first
- only escalate to a bigger build/test pass after the local failure is addressed
- if a command keeps failing with the same signature, stop broad retries and narrow scope
4. Report exact execution state
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 · 112 lines · 46 tokens per session scan A e43bed50a797
terminal-ops is a skill published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 679 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
agf
Find local coding-agent sessions, inspect bounded metadata or summaries, and prepare a read-only resume plan with AGF. Use for finding prior work across agent CLIs, not for executing agents, deleting sessions, or reading full transcripts.
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
janitor-fix
Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.
review-efficiency
Skill "review-efficiency" from dhaupin/vant, covering efficiency review, the question, what to check, 1. compute and 2. network.
rest
How to actually spend free time when it appears (drag: no productivity guilt, play stays play).
audit-deploy
Skill "audit-deploy" from dhaupin/vant, covering deploy audit, the question, what to check, 1. build and does build pass?.