Tracely is a CI/CD system for AI agents that turns failed production traces into replayable regression tests. Development teams use it to detect and group agent failures, run the resulting cases on pull requests, and block changes that reproduce those failures. The catalogue entries provide skills for operating this trace-based testing and observability workflow.
Borrowing it
Nothing to install: this file belongs to Jwuthri/Tracely-ai. 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/Jwuthri/Tracely-ai/master/.claude/skills/maintain-greptile-rules/SKILL.mdgit clone --depth 1 https://github.com/Jwuthri/Tracely-aiWrote 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/jwuthri/tracely-ai/maintain-greptile-rules)<a href="https://agentmods.dev/skills/jwuthri/tracely-ai/maintain-greptile-rules"><img src="https://agentmods.dev/badge/skills/jwuthri/tracely-ai/maintain-greptile-rules/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/jwuthri/tracely-ai/maintain-greptile-rules"><img src="https://agentmods.dev/badge/skills/jwuthri/tracely-ai/maintain-greptile-rules.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.00097 | $0.00928 |
| Opus 5 | $0.00048 | $0.00464 |
| Sonnet 5 | $0.00019 | $0.00186 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
maintain-greptile-rules 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 10d 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.
This is a copy
100% identical to maintain-greptile-rules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Greptile rules
Keep .greptile/ high-signal. A review finding is evidence to evaluate, not automatically a new rule.
1. Verify the finding
- Reproduce or trace the finding against the current repository, including the relevant call path, tests, and intentional exceptions.
- Read
.greptile/config.json,.greptile/rules.md, and.greptile/files.jsonbefore proposing a change. - Distinguish a newly introduced risk from adjacent legacy debt. Do not encode an unverified assumption or a one-off implementation detail.
- Repository absence is not policy evidence. If a reviewer infers a preference only because no current example exists, leave Greptile, code, and CI unchanged unless an owner explicitly adopts the policy.
2. Route it to the right mechanism
- One-off bug: fix the code and add a focused regression test. Do not add a Greptile rule.
- Verified deterministic policy violation: prefer TypeScript, Oxlint, Knip, a focused test, or CI.
- Repeatable, diff-enforceable invariant: add or refine a scoped structured rule in
.greptile/config.json. - Architecture, preference, or false-positive calibration: update
.greptile/rules.md. - Canonical implementation Greptile should consult: add a narrowly scoped reference in
.greptile/files.json. - Small workflow friction: use the
papercutsskill and log it in.agents/PAPERCUTS.md.
3. Apply the promotion bar
Promote a finding only when all applicable checks pass:
- It is verified against current code.
- A future reviewer can observe it from the diff and relevant call path.
- It is repository-specific or materially improves false-positive calibration.
- It is likely to recur, or its impact is high enough to justify prevention: authorization, security, billing, data loss, or cross-database correctness.
- Existing Greptile context and automated checks do not already cover it adequately.
- The instruction can be specific, measurable, narrowly scoped, and explicit about legitimate exceptions.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 63 lines · 97 tokens per session scan A 0028e9716262
maintain-greptile-rules is a skill published in the GitHub repository Jwuthri/Tracely-ai (1,221 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 928 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to maintain-greptile-rules, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
sprr
Single PR reviewer for awesome-quant. Use when the user asks to review, validate, comment on, label, close, or merge one specific pull request that adds README.md entries. Triggers include "sprr", "review PR", "check PR", and "validate contribution".
ln-41-test-strategy-planner
Plans a risk-based test portfolio and prioritized scenarios without editing tests. Not for test execution or implementation.
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…
bprr
Bulk PR reviewer for awesome-quant. Use when the user asks to review all open PRs, review unreviewed PRs, bulk review, or mentions "bprr". Reviews open PRs lacking the reviewed label and presents a summary before any merge/comment/label action.
squid-implement-night
Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.