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/petekp/claude-code-setup/circuit-resource-analysisnpx skills add petekp/claude-code-setup --skill circuit-resource-analysisgit clone --depth 1 https://github.com/petekp/claude-code-setupWrote 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/petekp/claude-code-setup/circuit-resource-analysis)<a href="https://agentmods.dev/skills/petekp/claude-code-setup/circuit-resource-analysis"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/circuit-resource-analysis.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.00100 | $0.01123 |
| Opus 5 | $0.00050 | $0.00562 |
| Sonnet 5 | $0.00020 | $0.00225 |
| Haiku 4.5 | $0.00010 | $0.00112 |
Grade A, and why
circuit-resource-analysis 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Circuit Resource Analysis
Overview
Analyze the resource for useful Circuit product learning. Focus on relation, contrast, feasibility, product impact, and whether the idea is worth saving.
Start With Source Truth
Use the strongest available source before giving conclusions.
- If the resource is pasted, analyze the pasted content.
- If the resource is a link, open or search for the source. Cite links used.
- If the resource is a local repo or codebase, inspect files directly.
- If the resource is a GitHub repo, inspect its README, examples, docs, and code paths that prove the relevant behavior.
- If the resource describes current Circuit behavior, verify against the local Circuit repo before claiming it is possible or impossible.
For Circuit repo work, read docs/release/v1-launch-plan.md first. Use
UBIQUITOUS_LANGUAGE.md for product vocabulary. For flow feasibility, prefer
current code and contracts over memory.
Useful Circuit anchors:
docs/release/v1-launch-plan.mdUBIQUITOUS_LANGUAGE.mddocs/flows/authoring-model.mddocs/flows/block-catalog.jsonsrc/flows/catalog.tssrc/flows/types.tsdocs/architecture/run-process.mddocs/ideas/README.mddocs/ideas/catalog.json
Classify The Resource
Name what kind of input it is before analyzing it:
- Codebase, repo, library, or tool
- Article, essay, paper, announcement, post, or conversation
- Workflow example
- Product pattern or competitor pattern
- Other
Then choose the matching analysis path below. If more than one applies, combine them.
Analyze Codebases And Articles
Answer these questions:
- What is the core idea?
- How does it relate to Circuit?
- How does it contrast with Circuit?
- What could Circuit learn from it?
- What could Circuit adapt or adopt?
- What would be a bad fit for Circuit, and why?
Prefer concrete product implications over a generic summary of the source. Separate facts from interpretation.
Analyze Workflow Examples
For workflows, be blunt about feasibility:
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.
- 3d ago First seen · 134 lines · 100 tokens per session scan A 5c12768ac519
circuit-resource-analysis is a skill published in the GitHub repository petekp/claude-code-setup (47 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 1,123 once invoked, about $0.0005 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
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
bootstrap-repo-analysis
First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
AI & LLM Security
LLM and AI application security testing — prompt injection, jailbreak resistance, OWASP LLM Top 10 (2025), RAG and agent/tool-use security, model supply chain, and AI red teaming for authorized assessments.
official-document-writing
专业的党政机关公文写作指南。当用户需要撰写、修改或审核党政机关公文（如请示、通知、函、总结、纪要等）时使用。提供GB/T 9704-2012格式规范指导、常用公文模板、语言规范建议和公文质量检查。适用于以下场景：(1) 撰写新公文，(2) 修改完善公文，(3) 检查公文格式规范，(4) 提供公文写作指导，(5) 审核公文质量。.