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 agentmods add skills/agent-sh/agentsys/perf-profilernpx skills add agent-sh/agentsys --skill perf-profilergit 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/perf-profiler)<a href="https://agentmods.dev/skills/agent-sh/agentsys/perf-profiler"><img src="https://agentmods.dev/badge/skills/agent-sh/agentsys/perf-profiler.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 | $0.00025 | $0.00214 |
| Opus 5 | $0.00013 | $0.00107 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
perf-profiler 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 4d 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
perf-profiler
Run profiling tools and capture hotspots with evidence.
Follow docs/perf-requirements.md as the canonical contract.
Parse Arguments
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const tool = args[0] || '';
const command = args.slice(1).join(' ');
Required Rules
- Verify debug symbols before profiling.
- Capture file:line for hotspots.
- Provide flame graph or equivalent output when possible.
Output Format
tool: <profiler>
command: <command>
hotspots:
- file:line - reason
artifacts:
- <path to flame graph or profile>
Constraints
- No profiling without a clear scenario.
- Keep outputs minimal and evidence-backed.
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.
- 4d ago First seen · 42 lines · 25 tokens per session scan A 41a0fa53f4a8
perf-profiler is a skill published in the GitHub repository agent-sh/agentsys (982 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 214 once invoked, about $0.0001 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
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
byterover
You MUST use this skill for: (1) 'Show me how ByteRover works', 'walk me through ByteRover', tour, intro, walkthrough, or onboarding requests — runs a guided 90-second introduction; (2) gathering contexts before any work; (3) saving knowledge after any change. ByteRover stores and retrieves project patterns…
zeroclaw
Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…