agentsys: Skill for Claude Code

.kiro/skills/perf-investigation-logger/SKILL.md

perf-investigation-logger is a skill for Claude Code, Kiro from agent-sh/agentsys. It costs 17 tokens per session (192 once invoked), scanned A, original, MIT.

A tool for appending structured notes about a performance investigation, meaning work to find and explain why software is slow. The notes include decisions, evidence, and the exact words used by the user.

In plain words
What is it for?
Use it to record investigation phases, user quotes, commands, metrics, file locations, summaries, and decisions in performance-investigation files.
Why use it?
It keeps the reasoning and supporting measurements in one consistent record. This makes it easier to review what was investigated, why choices were made, and where the evidence came from.

Skill for Claude CodeKiro

Written for Claude Code and Kiro: shipped in a Claude Code plugin, but also installed under .kiro/.

This is agent-sh/agentsys's own configuration. It tells Claude Code and Kiro how to work on agentsys itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentsys configures →

Part of the agentsys plugin — 28 skills, 1 hook shipped together

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/agent-sh/agentsys/main/.kiro/skills/perf-investigation-logger/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/agent-sh/agentsys

Made for: Claude Code, Kiro.

Or install agentsys, the plugin that ships this one along with the rest of its 28 skills, 1 hook.

Wrote 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.

agentmods badge for perf-investigation-logger

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-sh/agentsys/perf-investigation-logger/github.svg)](https://agentmods.dev/skills/agent-sh/agentsys/perf-investigation-logger)
Your own site
<a href="https://agentmods.dev/skills/agent-sh/agentsys/perf-investigation-logger"><img src="https://agentmods.dev/badge/skills/agent-sh/agentsys/perf-investigation-logger/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.

agentmods 80×15 button for perf-investigation-logger

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-sh/agentsys/perf-investigation-logger"><img src="https://agentmods.dev/badge/skills/agent-sh/agentsys/perf-investigation-logger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 192 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00192
Opus 5 $0.00009 $0.00096
Sonnet 5 $0.00003 $0.00038
Haiku 4.5 $0.00002 $0.00019

Measured 10d ago against content hash f21ce423a52e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

perf-investigation-logger 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 10d 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.

.kiro/skills/perf-investigation-logger/SKILL.md · 42 lines

What it actually says

perf-investigation-logger

Append structured investigation notes to {state-dir}/perf/investigations/<id>.md.

Follow docs/perf-requirements.md as the canonical contract.

Required Content

  1. Exact user quotes (verbatim)
  2. Phase summary
  3. Decisions and rationale
  4. Evidence pointers (files, metrics, commands)

Output Format

## <Phase Name> - <YYYY-MM-DD>

**User Quote:** "<exact quote>"

**Summary**
- ...

**Evidence**
- Command: `...`
- File: `path:line`

**Decision**
- ...

Constraints

  • Use AI_STATE_DIR for state path (default .claude).
  • Do not paraphrase user quotes.
Changes

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.

  1. 10d ago First seen · 42 lines · 17 tokens per session scan A f21ce423a52e

Subscribe to this mod's changes

perf-investigation-logger is a skill published in the GitHub repository agent-sh/agentsys (984 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 192 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.

Related

Other skills, from other repositories

omc-review

Evaluate finished work for defects, risk, and simplification before it ships.

Yeachan-Heo/oh-my-claudecode · 18 tokens

oracle

Oracle second-model review: bundle prompts/files, debug, refactor, design.

steipete/oracle · 18 tokens

review-loop

Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…

sangrokjung/claude-forge · 100 tokens

refactor

Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.

code-yeongyu/oh-my-openagent · 36 tokens

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…

code-yeongyu/oh-my-openagent · 161 tokens

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…

code-yeongyu/oh-my-openagent · 211 tokens