Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ShulkwiSEC/bb-hugenpx agentmods add skills/shulkwisec/bb-huge/insecure-source-code-managementWrote 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/shulkwisec/bb-huge/insecure-source-code-management)<a href="https://agentmods.dev/skills/shulkwisec/bb-huge/insecure-source-code-management"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/insecure-source-code-management/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/shulkwisec/bb-huge/insecure-source-code-management"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/insecure-source-code-management.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.00047 | $0.01441 |
| Opus 5 | $0.00023 | $0.00720 |
| Sonnet 5 | $0.00009 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
insecure-source-code-management 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 7d 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.
This is a copy
100% identical to insecure-source-code-management — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Insecure Source Code Management
AI LOAD INSTRUCTION: This skill covers detection and recovery of exposed version-control metadata, common backup artifacts, and related misconfigurations. Use only in authorized assessments. Treat recovered credentials and URLs as sensitive; do not exfiltrate real data beyond scope. For broad discovery workflow, cross-load recon-for-sec and recon-and-methodology when those skills exist in the workspace.
0. QUICK START
High-value paths to probe first (GET or HEAD, respect rate limits):
/.git/HEAD
/.git/config
/.svn/entries
/.svn/wc.db
/.hg/requires
/.bzr/README
/.DS_Store
/.env
Routing note: quickly probe these paths first; for full recon workflow, load methodology from recon-for-sec and recon-and-methodology before deeper testing.
1. GIT EXPOSURE
Detection
/.git/HEAD— valid repo often returns plain text like:
ref: refs/heads/main
/.git/config— may exposeremote.origin.url, user identity, or embedded credentials./.git/index,/.git/objects/— partial object store access enables reconstruction with the right tools.
403 vs 404
404— path likely absent or fully blocked at the edge.403on/.git/— directory may exist but listing is denied; still try direct file URLs:
/.git/HEAD
/.git/config
/.git/logs/HEAD
/.git/refs/heads/main
A 403 on the directory plus 200 on HEAD strongly indicates exposure.
Recovery tools (open source)
arthaud/git-dumper— dumps reachable.gittree when individual files are fetchable.internetwache/GitTools— Dumper, Extractor, Finder modules for partial/corrupt dumps.WangYihang/GitHacker— alternative recovery when standard dumpers miss edge cases.
Key files to prioritize
| Path | Why it matters |
|---|---|
.git/config |
Remotes, credentials, hooks paths |
.git/logs/HEAD |
Commit history, reflog-style leakage |
.git/refs/heads/* |
Branch tips, commit SHAs |
.git/packed-refs |
Packed branch/tag refs |
.git/objects/** |
Object blobs for reconstruction |
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.
- 7d ago First seen · 162 lines · 47 tokens per session scan A 7e033f796ec8
insecure-source-code-management is a skill published in the GitHub repository ShulkwiSEC/bb-huge (22 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,441 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to insecure-source-code-management, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pwn-aws-codecommit
Drive PWN::AWS::CodeCommit from pwneval.
git-history-analyzer
Use this agent when you need to understand the historical context of code changes, trace code pattern origins, or analyze commit history patterns. Unlike repo-research-analyst (repo structure and docs), this agent focuses on git log archaeology.
pr-comment-resolver
Use this agent when you need to address comments on pull requests or code reviews by making the requested changes and reporting back on the resolution.
archive-kb
This skill should be used when archiving completed knowledge-base artifacts (brainstorms, plans, specs) to their archive/ subdirectories with timestamp prefixes and git history preservation.
Hooks Automation
Automated coordination, formatting, and learning from Claude Code operations using intelligent hooks with MCP integration. Includes pre/post task hooks, session management, Git integration, memory coordination, and neural pattern training for enhanced development workflows.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…