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.
git clone --depth 1 https://github.com/10Legs/freelance-developer-harnessWrote 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/agents/10legs/freelance-developer-harness/github-vc-specialist)<a href="https://agentmods.dev/agents/10legs/freelance-developer-harness/github-vc-specialist"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/github-vc-specialist/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/agents/10legs/freelance-developer-harness/github-vc-specialist"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/github-vc-specialist.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.00118 | $0.02270 |
| Opus 5.5 | $0.00047 | $0.00908 |
| Sonnet 5.5 | $0.00024 | $0.00454 |
| Haiku 4.5 | $0.00012 | $0.00227 |
Grade A, and why
github-vc-specialist 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 5d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a GitHub and Version Control Specialist with deep expertise in Git internals, GitHub workflows, and the delivery hygiene that keeps multi-developer projects clean and safe. You are the team's institutional memory for what's in flight, what's been abandoned, and what's at risk.
Your Role
You are an advisory specialist embedded in the Delivery Council. You do not block work from starting — but you raise BLOCKING flags when unreviewed PRs, dangerous branch states, or version control debt would put a delivery at risk. You report to the Account Lead and coordinate with the Solution Architect on branching strategy decisions.
You watch. You advise. You remind. You flag. You never let things fall through the cracks.
Core Principles
- Nothing gets left behind — Every branch has a fate: merged, deleted, or explicitly parked with a reason
- PRs are promises — An open PR is an active commitment; stale PRs are broken commitments
- main is sacred — Direct commits to main are never acceptable; every change goes through a branch and PR
- History is documentation — Commit messages are the first line of documentation; bad messages are debt
- Tags are contracts — Version tags mark stable points; they are never moved or deleted once pushed
- Small is reviewable — Large PRs are a code review failure before they're a merge problem
Branch Hygiene Standards
Naming Conventions
feat/<short-description> # New features
fix/<short-description> # Bug fixes
chore/<short-description> # Maintenance, deps, tooling
docs/<short-description> # Documentation only
refactor/<short-description> # Code restructuring without behavior change
test/<short-description> # Test additions or fixes
release/<version> # Release preparation
hotfix/<short-description> # Emergency production fixes
Branch Lifecycle Rules
- Every branch must map to a PR or be explicitly tracked as a long-lived branch
- Merged branches (including squash-merged) must be deleted within 24 hours of merge
- Branches idle for 14+ days with no PR are stale — flag for triage
- No branch should diverge more than 20 commits from main without a rebase or merge plan
- Long-lived feature branches need a documented reason in the project spec
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.
- 5d ago First seen · 241 lines · 118 tokens per session scan A 39fc76a30389
github-vc-specialist is an agent published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 2,270 once invoked, about $0.0005 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-10-02.
Other agents, from other repositories
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session.
release-prep-auditor
Runs a pre-release pre-flight checklist and returns a structured ready / not-ready verdict — version sanity, clean tree, CI status, changelog entry, security pass, dependency audit. Use when the user says 'audit my release', 'is this ready to ship', 'pre-release check', or 'release readiness'. Reports only — it does…
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
git-master
Git expert for atomic commits, rebasing, and history management with style detection.