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 skills add strikersam/autonomous-ai-agency --skill repowise-intelligencegit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/repowise-intelligence)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/repowise-intelligence"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/repowise-intelligence/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/strikersam/autonomous-ai-agency/repowise-intelligence"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/repowise-intelligence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 12 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 13 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00042 | $0.01195 |
| Opus 5 | $0.00021 | $0.00598 |
| Sonnet 5 | $0.00008 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
repowise-intelligence 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 11d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: repowise-intelligence
Purpose
Provides codebase intelligence layers inspired by repowise (https://github.com/repowise-dev/repowise). Enables AI agents to understand the repository at a deeper level through:
- Dependency graph intelligence (file and symbol relationships)
- Git intelligence (history, ownership, co-changes)
- Documentation intelligence (auto-generated docs with freshness scoring)
- Decision intelligence (architectural decisions from git history)
When to Use
- When an agent needs to understand "why" code was built a certain way
- Before making significant changes to understand impact and relationships
- When trying to reduce token usage by getting targeted context instead of reading full files
- When implementing features that benefit from understanding code ownership and change patterns
- When needing to answer complex questions about the codebase efficiently
Directory Structure
This skill creates and manages:
.Codex/skills/repowise-intelligence/
intelligence/ ← Intelligence data storage
dependency_graph.json ← File and symbol dependency graph
git_history.json ← Git history analysis (hotspots, ownership, co-changes)
documentation/ ← Auto-generated documentation for modules/files
decisions.json ← Architectural decisions extracted from git history
INDEX.md ← Overview of available intelligence
Intelligence Layers
1. Graph Intelligence (Dependency Graph)
- Parses files to build file-level and symbol-level dependency graphs
- Handles import aliases, barrel re-exports, namespace imports
- Tracks heritage (extends, implements, etc.)
- Uses community detection to find logical modules
- Calculates centrality measures (PageRank, betweenness) to identify important code
2. Git Intelligence
- Analyzes git history for:
- Hotspot files (high churn × high complexity)
- Ownership percentages per contributor
- Co-change pairs (files that change together without import links)
- Significant commit messages explaining evolution
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.
- 11d ago First seen · 131 lines · 42 tokens per session scan A a2bd1ba5e912
repowise-intelligence is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,195 once invoked, about $0.0002 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-31.
Other skills, from other repositories
state-management
STATE.md reading, writing, and field-level updates. Provides cross-session state persistence via .planning/STATE.md with structured fields for current task, completed phases, blockers, decisions, and quick tasks.
mem0-integration
Mem0 memory layer integration for AI agents. Implement persistent, semantic memory for long-term context retention and personalization.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
persistent-memory
Observation capture and retrieval across sessions. Stores decisions, discoveries, and bugfix patterns. Searchable via tags and relevance scoring.
context-management
Project context loading, isolation, and persistent state management across CCPM sessions.
memclaw
The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a caura…