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/matteing/opal/gitnpx skills add matteing/opal --skill gitgit clone --depth 1 https://github.com/matteing/opalWhat 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.00033 | $0.00764 |
| Opus 5 | $0.00016 | $0.00382 |
| Sonnet 5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
git 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Conventional Commit Skill
You enforce Conventional Commits on every commit in this repository. This is critical for consistent changelogs and semantic version bumps.
Commit message format
Every commit message MUST follow this format:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types (required)
| Type | When to use | Version bump |
|---|---|---|
feat |
A new feature or capability | minor |
fix |
A bug fix | patch |
docs |
Documentation only | none |
style |
Formatting, semicolons, whitespace — no logic | none |
refactor |
Code change that neither fixes a bug nor adds a feature | none |
perf |
Performance improvement | patch |
test |
Adding or correcting tests | none |
build |
Build system or external dependency changes | none |
ci |
CI configuration changes | none |
chore |
Maintenance tasks (deps, tooling, releases) | none |
Scopes (recommended)
Use a scope to identify the affected area:
| Scope | Meaning |
|---|---|
core |
Elixir core (lib/opal/ directory) |
cli |
TypeScript CLI (cli/ directory) |
rpc |
JSON-RPC protocol layer |
agent |
Agent loop / GenServer |
tools |
Built-in tool implementations |
ci |
GitHub Actions workflows |
release |
Release and versioning infrastructure |
docs |
Documentation |
sdk |
TypeScript SDK client |
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 · 89 lines · 33 tokens per session scan A 30d96b44d988
git is a skill published in the GitHub repository matteing/opal (58 stars, last pushed 20d ago), licensed MIT. It adds 33 tokens to every session and 764 once invoked, about $0.0002 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
agent-pattern-verification
Verify AI agent code for dangerous patterns including infinite loops, unbounded retries, tool hallucinations, and context overflow. Use before deploying agent workflows or when reviewing agent code.
cloudflare-agent
Enable ControlKeel governance for Cloudflare Agents with policy gates, budget enforcement, PII detection, and secure execution.
controlkeel-governance
Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.
bounded-loop
Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.
challenge
Adversarially challenge the current plan or finding. Assume the direction is wrong and build the strongest case against it. Surfaces blind spots, false assumptions, and unexplored alternatives before execution starts.
continuity
Learn, record, audit, and apply codebase patterns consistently across a repo by comparing current code to canonical local examples stored in CK memory. Use when asked to preserve continuity, learn a pattern, check drift, fix inconsistent implementations, or enforce local conventions.