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 resource-panelgit 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/resource-panel)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/resource-panel"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/resource-panel/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/resource-panel"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/resource-panel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 44 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.00000 | $0.00681 |
| Opus 5 | $0.00000 | $0.00341 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
resource-panel 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 12d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: resource-panel
Purpose
Track, display, and summarise all resources consumed or produced during an agent session: files read/written, URLs fetched, tools called, tokens used, and external dependencies touched.
Inspired by Copilot's resource panel UI — gives operators a single-pane-of-glass view of what an agent actually touched.
When to Use
- After any multi-step implementation task
- During code review to understand blast radius
- In CI to surface unexpected file or network access
- As a pre-commit audit
Output Format
The resource panel is emitted as a fenced Markdown block:
╔══════════════════════════════════════════════════════╗
║ RESOURCE PANEL ║
╠══════════════════════════════════════════════════════╣
║ FILES READ │ 12 files ║
║ FILES WRITTEN │ 5 files ║
║ URLS FETCHED │ 3 URLs ║
║ TOOLS CALLED │ Bash(8) Read(12) Write(5) ║
║ EXTERNAL DEPS │ npm:lodash, pip:requests ║
╠══════════════════════════════════════════════════════╣
║ CHANGED FILES ║
║ src/index.ts [modified] ║
║ src/utils/parser.ts [created] ║
║ tests/parser.test.ts [created] ║
╠══════════════════════════════════════════════════════╣
║ URLS ║
║ https://example.com/api [fetched] ║
╚══════════════════════════════════════════════════════╝
How to Use
Ask Claude to emit a resource panel
At the end of your task prompt, add:
When done, emit a resource-panel summary following .agents/skills/resource-panel/SKILL.md
Automated via shell (git-based)
bash .agents/skills/resource-panel/summarise.sh
This script uses git diff --name-only and git status to auto-generate the panel for the current working tree.
Fields
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 78 lines · 0 tokens per session scan A d88726c71c4b
resource-panel is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 681 tokens. 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
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
guardrails-ai-setup
Guardrails AI validation framework setup for LLM applications. Implement input/output validation, safety checks, and structured output enforcement.
mcp-app-scaffolding
Scaffolds MCP App project structure with correct directory layout, dependencies, entry points, and framework-specific templates. Handles React (useApp hook), Vanilla JS, Vue, Svelte, Preact, and Solid.
mcp-csp-investigation
Comprehensive Content Security Policy audit for MCP Apps in sandboxed iframes. Discovers all network origins, traces them to source, and generates CSP configuration for registerAppResource.