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 rules/comet-ml/opik/git-workflowgit clone --depth 1 https://github.com/comet-ml/opikWhat 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.00599 | $0.00599 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
git-workflow 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Branch Naming
{username}/{ticket}-{summary}
andrescrz/OPIK-2180-add-featureuser/issue-123-fix-buguser/NA-hotfix-description
Commit Format
First commit in branch (used as PR title source):
[<TICKET-KEY>] [COMPONENT] <type>: description
[OPIK-1234] [BE] feat: add create trace endpoint[issue-123] [FE] fix: guard empty state[NA] [DOCS] docs: update API documentation
Follow-up commits (preferred):
<type>(<scope>): description
feat(metrics): add project chart filtersfix(api): handle null feedback scoretest(backend): cover trace creation
Revision N: ... is a last-resort fallback only.
PR Title
[<TICKET-KEY>] [COMPONENT] <type>: description
Jira Key References (commit messages & PR body)
The GitHub for Jira app links a PR to a ticket's Development panel whenever it finds an issue key matching [A-Z][A-Z0-9]+-\d+ (project key, literal hyphen, digits) in the branch name, PR title, PR body, or any commit message. It matches on the regex alone — it cannot tell "this PR resolves the ticket" from "this just mentions it" — and the resulting link cannot be removed afterward. So free text must only contain hyphenated keys for tickets the PR actually resolves.
- Tickets this PR resolves → keep the hyphen:
OPIK-1234. Jira links/URLs are fine and wanted (you want these to link). A PR may resolve more than one ticket — list every resolved key this way. - Tickets related but not resolved in this PR (e.g. an escalation, or a fix that references an older ticket — anything not in the PR title or branch):
- Replace the hyphen with an underscore:
OPIK_7000. The underscore breaks the literal-the scanner requires, so the key cannot match. - Do not paste a Jira URL for them either —
.../browse/OPIK-7000contains the hyphenated key and would link anyway. Backticks/parentheses do not help; only breaking the hyphen does.
- Replace the hyphen with an underscore:
Branch name, PR title, and the PR template's ## Issues section are unaffected — resolved keys use normal OPIK-1234 there.
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 · 47 lines · 599 tokens per session scan A 2a977074bfa6
git-workflow is a cursor rule published in the GitHub repository comet-ml/opik (21,685 stars, last pushed 2d ago), licensed Apache-2.0. It adds 599 tokens to every session, about $0.0030 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 cursor rules, from other repositories
cursorrules
Always follow these rules when developing in this workspace.
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
lean
Answer densely. Cut filler, keep all technical signal.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.