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/sachinshelke/codevira/open-source-qualitynpx skills add sachinshelke/codevira --skill open-source-qualitygit clone --depth 1 https://github.com/sachinshelke/codeviraWrote 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/sachinshelke/codevira/open-source-quality)<a href="https://agentmods.dev/skills/sachinshelke/codevira/open-source-quality"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/open-source-quality.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.00101 | $0.01733 |
| Opus 5 | $0.00051 | $0.00866 |
| Sonnet 5 | $0.00020 | $0.00347 |
| Haiku 4.5 | $0.00010 | $0.00173 |
Grade A, and why
open-source-quality 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open-source quality — non-skippable checks at commit time
The codevira repo is open-source. Every commit ends up in git log
that future contributors read to learn the codebase. Bad commits =
unreadable history = onboarding pain for everyone who comes after.
When this skill triggers, walk through the checklist below BEFORE
calling the Bash tool with git commit. Skip a step → commit is
not ready.
Commit message discipline
Conventional Commits format
Every commit message follows: type: short imperative summary
Types:
feat:— new feature (user-visible)fix:— bug fix (user-visible)docs:— documentation onlyrefactor:— code restructure, no behavior changetest:— adding or fixing testschore:— build, tooling, depsrelease:— version bump for publishingperf:— performance improvementstyle:— formatting / whitespace
Subject line:
- Imperative mood: "add foo" not "added foo"
- < 70 characters
- No trailing period
- Lowercase after the type
Atomic commits
One logical change per commit. Examples:
- ✗ "fix bug and refactor tests and update docs" → 3 commits
- ✓ "fix(indexer): single matcher between configure and index"
- ✓ "test(indexer): regression test for split-config bug"
- ✓ "docs: explain shared file matcher in indexer README"
If your diff spans 3 unrelated concerns, split into 3 commits before
pushing. Use git add -p (interactive staging) or commit-by-file.
Body explains WHY
Subject is WHAT. Body is WHY.
fix(indexer): single matcher between configure and index
Previously configure used discover_source_files() but index used a
separate hand-rolled matcher in cmd_incremental. They diverged: docs-
only repos passed configure but failed indexing silently.
The split was a latent bug since v1.6 when discover_source_files
landed. Unifying eliminates the entire class of "discovery vs
indexing" mismatches surfaced as Bug A in the 2026-05-15 audit.
Co-Authored-By: <name>
Code style
Before commit, ALL of these must pass:
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 · 228 lines · 101 tokens per session scan A f6dbe789f187
open-source-quality is a skill published in the GitHub repository sachinshelke/codevira (12 stars, last pushed 19d ago), licensed MIT. It adds 101 tokens to every session and 1,733 once invoked, about $0.0005 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-30.
Other skills, from other repositories
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.
spec-checkpoint
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".