Borrowing it
Nothing to install: this file belongs to kissrosecicd-hub/agents-evolution. 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/kissrosecicd-hub/agents-evolution/main/.agents/skills/deepsource-platform/SKILL.mdgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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/kissrosecicd-hub/agents-evolution/deepsource-platform)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/deepsource-platform"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/deepsource-platform/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/kissrosecicd-hub/agents-evolution/deepsource-platform"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/deepsource-platform.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.00044 | $0.00602 |
| Opus 5.5 | $0.00018 | $0.00241 |
| Sonnet 5.5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
deepsource 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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepSource CLI
Authentication
deepsource auth login
Goals
Get code review issues
deepsource issues --output json
Narrow by severity, category, or path:
deepsource issues --severity critical,major --output json
deepsource issues --category security,bug-risk --output json
deepsource issues --path src/auth --output json
deepsource issues --severity critical --category security --limit 20 --output json
Scope to a PR or branch:
deepsource issues --pr 42 --output json
deepsource issues --default-branch --output json
Get report card
deepsource report-card --output json
Returns grades (A-F) and scores for security, reliability, complexity, hygiene, coverage, and an aggregate.
Scope to a PR or commit:
deepsource report-card --pr 42 --output json
deepsource report-card --commit abc123 --output json
Get vulnerabilities
deepsource vulnerabilities --output json
Filter by severity:
deepsource vulnerabilities --severity critical,high --output json
Scope to a PR or branch:
deepsource vulnerabilities --pr 42 --output json
deepsource vulnerabilities --default-branch --output json
Check analysis status
deepsource repo status --output json
deepsource runs --output json
deepsource runs --commit abc123 --output json
repo status shows activation and configured analyzers. runs shows recent analysis run history.
Key patterns
- Auto-detection: Inside a git repo the CLI auto-detects the repo and current branch. Use
--repowhen outside the repo or targeting a different one. Use scope flags (--pr,--commit,--default-branch) to override the auto-detected branch. - Always use
--output jsonfor machine-readable output. - Repo format:
--repo provider/owner/name— providers:gh,gl,bb,ads. - Scope flags are mutually exclusive:
--commit,--pr, and--default-branchcannot be combined. Omit all three to use auto-detection.
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.
- 1mo ago First seen · 94 lines · 44 tokens per session scan A 10fa05914027
deepsource is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 602 once invoked, about $0.0002 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…