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/d-oit/rust-2026-template/dora-reportnpx skills add d-oit/rust-2026-template --skill dora-reportgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/dora-report)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/dora-report"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/dora-report.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00980 |
| Opus 5 | $0.00026 | $0.00490 |
| Sonnet 5 | $0.00010 | $0.00196 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
dora-report 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 4d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: dora-report
When to Use
- User asks for this skill's functionality
Purpose
Generate a DORA-REPORT.md for this repository by computing the five core DORA software
delivery performance metrics and three DORA agentic metrics from available data sources.
When to use
- When asked to generate a DORA report or assess delivery performance
- During sprint reviews or quarterly assessments
- When evaluating the ROI of AI tooling adoption
- Run this skill monthly to track trends
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Python 3.9+ available
.agents/metrics.jsonlexistsdora-metrics.jsonlexists
Steps
1. Fetch Deployment Frequency data from GitHub API
gh api "/repos/{owner}/{repo}/releases" --paginate \
--jq '[.[] | {tag: .tag_name, published: .published_at}]' \
> /tmp/releases.json
2. Fetch PR Lead Time data
gh api "/repos/{owner}/{repo}/pulls?state=closed&base=main" --paginate \
--jq '[.[] | select(.merged_at != null) | {pr: .number, created: .created_at, merged: .merged_at}]' \
> /tmp/prs.json
3. Run the compute script
python3 .agents/skills/dora-report/scripts/compute_dora.py \
--releases /tmp/releases.json \
--prs /tmp/prs.json \
--agent-metrics .agents/metrics.jsonl \
--dora-metrics dora-metrics.jsonl \
--template .agents/skills/dora-report/templates/DORA-REPORT.md.jinja \
--output reports/DORA-REPORT.md \
--period-days 30 \
--repo $(git remote get-url origin | sed 's/.*github.com[:\/]\(.*\)\.git/\1/')
4. Review and commit the report
git add reports/DORA-REPORT.md
git commit -m "docs(dora): update reports/DORA-REPORT.md [skip ci]"
5. Log the report generation in metrics.jsonl
Append to .agents/metrics.jsonl:
echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","agent":"claude","skill":"dora-report","task_description":"Generated monthly DORA report","success":true,"human_interventions":0}' >> .agents/metrics.jsonl
What ships with it
4 files 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.
- 4d ago First seen · 114 lines · 52 tokens per session scan A 7c77d4f09623
dora-report is a skill published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 980 once invoked, about $0.0003 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-31.
Other skills, from other repositories
greptimedb-development-docker-image
Builds a development-only GreptimeDB Docker image from a local debug binary for local-cluster testing, and optionally pushes it to a development registry. Use when the user asks to package, build, tag, publish, or cross-build a non-release GreptimeDB or GreptimeDB Enterprise image for debugging.
greptimedb-fuzz-ci-failure-investigation
Investigate a failed GreptimeDB fuzz CI target link by downloading GitHub Actions job logs plus fuzz artifacts such as kind logs, monitor dumps, and CSV dumps, then correlate the failure with local GreptimeDB source code. Use when the user provides a failed fuzz CI target/job URL or asks to diagnose GreptimeDB fuzz CI…
greptimedb-release-note
Generate a GreptimeDB release changelog with git cliff (correct range, subtract already-released patch PRs, rebuild contributors, add human-curated highlights), output to a file, and prepare the docs-repo blog PR. Use when asked to write/generate a GreptimeDB release note or changelog.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
stack-merge
Bulk-merge a Graphite stack into main via admin-bypass fast-forward push. Replaces the Graphite merge queue for rivet-dev/rivet. Invoke when the user says "merge the stack at ", "ship everything through ", "bulk-merge up to ", "fast-forward main to ", or any request to land multiple stacked PRs at once in one shot.…