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/m-binimran/dev-pack/perf-budgetnpx skills add m-binimran/dev-pack --skill perf-budgetgit clone --depth 1 https://github.com/m-binimran/dev-packWrote 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/m-binimran/dev-pack/perf-budget)<a href="https://agentmods.dev/skills/m-binimran/dev-pack/perf-budget"><img src="https://agentmods.dev/badge/skills/m-binimran/dev-pack/perf-budget.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.00045 | $0.00356 |
| Opus 5 | $0.00023 | $0.00178 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
perf-budget 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-budget
The budget
- LCP < 2.5s · CLS < 0.1 · INP < 200ms (the three Core Web Vitals).
- JS shipped to the client kept lean; flag large client bundles.
Checks & fixes
- Images: use
next/image(lazy, sized, modern formats). Setwidth/heightto reserve space → fixes CLS. - Fonts:
next/font(self-hosted,display: swap) — no layout shift, no render-block. - Client JS: prefer Server Components;
"use client"only where needed.dynamic()import heavy/below-fold components. Watch big date/icon/chart libs. - LCP element: make the hero image/text fast —
priorityon the LCP image, no blocking work above it. - Caching: static where possible; sensible
revalidate.
Measure, don't guess
- Run Lighthouse /
next buildand read the real numbers. Report measured values against the budget. - If you can't measure in this environment, say the budget is "designed for" not "verified."
Output
- Each metric: target vs. measured (or "unmeasured"), and the fix for any miss.
Guardrails
- Don't claim a CWV pass without a real measurement.
- Don't ship a render-blocking third-party script without justifying it.
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 · 30 lines · 45 tokens per session scan A 2bb14a8929de
perf-budget is a skill published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 356 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
investigate-issue
Investigate a GitHub issue by fetching details, analyzing the codebase, researching documentation, and presenting an actionable implementation plan with test guidance. Use when asked to investigate, analyze, triage, or plan work for a GitHub issue. Invoked with /investigate-issue or /investigate-issue (prompts for ID).
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
resolve-pr-comments
Skill "resolve-pr-comments" from maximhq/bifrost, covering resolve pr comments, usage, workflow overview, step 1: detect repository and step 2: fetch unresolved comments (graphql).
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
trulens-blocking-guardrails
Configure and use feedback functions as runtime blocking guardrails.