Borrowing it
Nothing to install: this file belongs to agent-sh/agentsys. 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/agent-sh/agentsys/main/.kiro/skills/repo-intel/SKILL.mdgit clone --depth 1 https://github.com/agent-sh/agentsysWrote 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/agent-sh/agentsys/repo-intel)<a href="https://agentmods.dev/skills/agent-sh/agentsys/repo-intel"><img src="https://agentmods.dev/badge/skills/agent-sh/agentsys/repo-intel.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.00050 | $0.00474 |
| Opus 5 | $0.00025 | $0.00237 |
| Sonnet 5 | $0.00010 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
repo-intel 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.
What it actually says
Repo Intel Skill
Unified static analysis - git history intelligence, AST symbol mapping, and project metadata via agent-analyzer.
Parse Arguments
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const action = args.find(a => !a.startsWith('--')) || 'status';
const force = args.includes('--force');
Primary Responsibilities
- Initialize on demand (
/repo-intel init) - Update incrementally (
/repo-intel update) - Query git history data (
/repo-intel query hotspots) - Check status and staleness (
/repo-intel status) - Validate output with the map-validator agent
Core Data Contract
Repo intel data is stored in the platform state directory:
- Claude Code:
.claude/repo-intel.json,.claude/repo-map.json - OpenCode:
.opencode/repo-intel.json,.opencode/repo-map.json - Codex CLI:
.codex/repo-intel.json,.codex/repo-map.json
Behavior Rules
- Never install dependencies without explicit user consent
- Always validate output with
map-validatorafter init/update - Prefer incremental update unless data is stale or history rewritten
When to Suggest Repo Intel
If a user asks for drift detection, documentation alignment, or repo analysis and repo-intel data is missing:
Repo intel data not found. For better analysis, run:
/repo-intel init
Staleness Signals
- Data commit not found (rebased)
- Branch changed
- Git hooks marked stale
- Commits behind HEAD
Output Expectations
Keep outputs concise:
- init/update: file count, symbol count, commit, warnings
- query: formatted query results
- status: staleness, commits behind, last updated
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 · 64 lines · 50 tokens per session scan A 0dcb0fc9c368
repo-intel is a skill published in the GitHub repository agent-sh/agentsys (982 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 474 once invoked, about $0.0003 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
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
code-review
Review the current diff, or a PR number/branch/path target, for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud); with no level…
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.