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 Team-Deepiri/deepiri-axiom --skill deepiri-sorgegit clone --depth 1 https://github.com/Team-Deepiri/deepiri-axiomWrote 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/team-deepiri/deepiri-axiom/deepiri-sorge)<a href="https://agentmods.dev/skills/team-deepiri/deepiri-axiom/deepiri-sorge"><img src="https://agentmods.dev/badge/skills/team-deepiri/deepiri-axiom/deepiri-sorge/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/team-deepiri/deepiri-axiom/deepiri-sorge"><img src="https://agentmods.dev/badge/skills/team-deepiri/deepiri-axiom/deepiri-sorge.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.00055 | $0.00689 |
| Opus 5 | $0.00028 | $0.00345 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
deepiri-sorge 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 11d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deepiri Sorge
Repo: deepiri-sorge — distributed AI PR review bot (GitHub Actions + optional Gemini/GitHub Models).
When to use this skill
- Opening or updating a PR that needs a first-pass AI review
- Wiring Sorge into a Deepiri repo (workflow + config + secrets)
- Interpreting Sorge comments or skip messages
- User says
/sorge, "sorge", or "AI PR review"
Trigger a review (/sorge)
- Ensure the PR exists and is pushed to GitHub.
- Comment
/sorgeon the PR (issue comment body is exactly/sorge, optionally with a short note after). - Treat the bot reply as a first pass that informs — not replaces — manual review.
- Fold Blocking / Important findings into the human review; do not merge on Sorge alone.
Also auto-runs on pull_request opened/synchronize/reopened (and configurable push) when the reusable workflow is installed.
Agent checklist (ship a PR)
- Push branch; open PR against
mainordevas repo policy requires - Comment
/sorgeon the PR - Wait for the review comment (or skip notice)
- Address real issues; re-comment
/sorgeafter large follow-up pushes if needed - Complete human/CI review gates before merge
Install into a repo
- Add
.github/workflows/pr_review.ymlcalling the Sorge workflow (seedeepiri-sorgeREADME), or copy the workflow from that repo. - Optional root
sorge.toml— defaults are fine for most repos. - Repo secret
GOOGLE_API_KEY(Gemini) when using Gemini routing;GITHUB_TOKENis provided by Actions. - Align with branch protection — Sorge comments are advisory unless the team explicitly requires a Sorge check.
Minimal sorge.toml
[sorge]
enabled = true
[filters]
min_lines = 20
skip_docs = true
skip_deps = true
[review]
style = "concise"
include_security = true
include_performance = true
Local dry-run (no PR comment)
cd deepiri-sorge # or sibling clone from .axiom/ecosystem.json
poetry install # or pip install -r requirements.txt
git -C <target-repo> diff origin/main...HEAD > /tmp/pr.diff
python -m bot.main --diff /tmp/pr.diff --dry-run --verbose
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.
- 11d ago First seen · 66 lines · 55 tokens per session scan A ec0f9cad36f3
deepiri-sorge is a skill published in the GitHub repository Team-Deepiri/deepiri-axiom (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 689 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
gemini-review
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration.
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.
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
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.
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
review
Review before merge. Stage-1 spec-compliance gate, then risk-selected Stage-2 review axes from the canonical set. analyst always runs, callers can pin extra always-on axes, and explicit deep review runs the full 16-axis set. Run after /test. Do NOT invoke code-qualities-assessment, doc-accuracy, golden-principles, or…