Borrowing it
Nothing to install: this file belongs to sachinshelke/codevira. 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/sachinshelke/codevira/main/.claude/skills/open-source-quality/SKILL.mdgit 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/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/sachinshelke/codevira/open-source-quality"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/open-source-quality.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.00101 | $0.01733 |
| Opus 5.5 | $0.00040 | $0.00693 |
| Sonnet 5.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 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 — 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.
- 1mo 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 1mo ago), licensed MIT. It adds 101 tokens to every session and 1,733 once invoked, about $0.0004 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.
to-code
Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
to-stack
Split a large branch or PR into a stack of small PRs, verified layer by layer, and open them as linked drafts.
polya-code
Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
commit
Group unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing or pull requests (/to-pr).