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/dmythro/agent-skills/git-cinpx skills add dmythro/agent-skills --skill git-cigit clone --depth 1 https://github.com/dmythro/agent-skillsWrote 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/dmythro/agent-skills/git-ci)<a href="https://agentmods.dev/skills/dmythro/agent-skills/git-ci"><img src="https://agentmods.dev/badge/skills/dmythro/agent-skills/git-ci.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.1 | $0.00088 | $0.02004 |
| Opus 5 | $0.00044 | $0.01002 |
| Sonnet 5 | $0.00018 | $0.00401 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
git-ci 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 6d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Status Queries
Query CI/CD pipelines and check merge readiness across GitHub Actions and GitLab CI. All recipes use minimal field sets for token efficiency. Covers pipeline status, failing jobs, run logs, workflow management, and merge readiness assessment.
When to Use
- Checking CI status -- "are checks passing?", "what's failing?", pipeline status
- Watching CI runs -- wait for completion, fail-fast on errors
- Debugging failures -- view logs for failing jobs, identify flaky tests
- Assessing merge readiness -- all checks green, reviews approved, no conflicts
- Listing workflow runs -- recent pipelines, specific workflow history
- Configuring CI allowlists -- auto-approval patterns for read-only CI commands
Critical Rules
- Use
gh pr checks(notgh run) for current-branch CI status. Thepr checkssubcommand maps directly to the PR's required status checks. - Use
glab ci statusfor current-branch CI in GitLab. It shows the pipeline for the current branch without needing a pipeline ID. - Always use
--jsonwithghto filter output fields. Full JSON output wastes tokens.gh pr checksaccepts exactlybucket,completedAt,description,event,link,name,startedAt,state,workflow-- there is noconclusionfield here (that one belongs togh runand tostatusCheckRollup), and an unknown field aborts the command withUnknown JSON field. - A green check is not always a completed job -- read
description. App and bot checks reportstate: SUCCESS/bucket: passfor outcomes that did no work: CodeRabbit postsReview rate limitedas a successful check when it never reviewed the code.descriptionis where the outcome lives, it is not returned by default, andgh pr view --json statusCheckRollupdrops it entirely. See Review-Bot Checks below before calling a PR reviewed or merge-ready. - Use commands exactly as shown in this skill. The commands below are designed to match auto-approval allowlist patterns. Improvising flags may trigger permission prompts.
What ships with it
2 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.
- 6d ago First seen · 184 lines · 88 tokens per session scan A 3b9d6576ae51
git-ci is a skill published in the GitHub repository dmythro/agent-skills (6 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 2,004 once invoked, about $0.0004 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
edge-case-hunter
Focuses specifically on unusual inputs, boundary conditions, empty states, and unexpected user behavior that implementations commonly miss. Use to find what a normal test pass would skip over.
flaky-test-diagnoser
Diagnoses why a test passes sometimes and fails others - timing, shared state, ordering dependence, or external dependencies - and proposes a fix. Use when a test fails intermittently.
bug-hunter
Searches code specifically for potential bugs, edge cases, race conditions, and incorrect assumptions rather than general style/quality. Use when the goal is finding what's broken, not improving what already works.
performance-auditor
Looks for performance bottlenecks across frontend rendering, backend logic, database access, and network usage. Use when something is slow or before it needs to scale.
cron-expression-translator
Translates cron expressions to plain English and back. Use when a cron schedule in code/config is unclear, or when you know when something should run but not the cron syntax for it.
concurrency-race-detector
Identifies race conditions, mutex contention, unsafe shared state, and deadlocks in concurrent and async code.