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/griffinwork40/agent-framework/forge-frictionnpx skills add griffinwork40/agent-framework --skill forge-frictiongit clone --depth 1 https://github.com/griffinwork40/agent-frameworkWrote 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/griffinwork40/agent-framework/forge-friction)<a href="https://agentmods.dev/skills/griffinwork40/agent-framework/forge-friction"><img src="https://agentmods.dev/badge/skills/griffinwork40/agent-framework/forge-friction.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.01550 |
| Opus 5 | $0.00013 | $0.00775 |
| Sonnet 5 | $0.00005 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
forge-friction 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the friction analyzer to get a summary of recent friction patterns:
python3 "${PLUGIN_ROOT}/scripts/friction/analyzer.py"
If no friction sessions exist, tell the user there are no friction patterns in the lookback window.
If friction data exists, review the output. It contains friction categories ranked by confidence, then frequency, each with recent examples showing friction_detail (what went wrong) and goal (what the user was trying to do).
Tool-error categories carry a failure-class suffix. :timeout, :truncated, and :slow are high-confidence — real, specific friction a skill can address — and rank first. :plain is the low-confidence residue: a fast non-zero exit the trace cannot distinguish from a benign result (a grep no-match, a test that exits 1). It ranks last and should be treated with skepticism.
Dry-run mode
If $ARGUMENT contains --dry-run: after the analyzer runs, identify themes using the filter criteria in "Your job" below, but instead of presenting them interactively, output a single markdown table:
| Category | Count | Example friction_detail |
|---|---|---|
| ... | N | "truncated quote 1"; "truncated quote 2" |
One row per theme. Truncate each friction_detail to ~80 chars. Up to 3 examples per row (semicolon-separated in the cell). If no themes pass the filter, print "No themes in lookback window."
After the table (or "no themes" line), print:
dry-run: no /forge invocation, no telemetry written
Stop. Do NOT proceed to the y/n prompts, /forge dispatch, or telemetry write described in "Your job" — those are skipped entirely in dry-run.
Auto mode
If $ARGUMENTS contains --auto: skip all y/n prompts and auto-approve all qualifying themes. For each theme that passes the filter criteria (3+ sessions, recurring failure mode, skill-addressable), immediately run /forge with the theme as a seed. Chain the invocations sequentially, then log telemetry for each generated skill. --auto respects --dry-run (if both flags are present, dry-run takes precedence and no /forge invocation or telemetry occurs).
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 · 94 lines · 25 tokens per session scan A 32e76a02f012
forge-friction is a skill published in the GitHub repository griffinwork40/agent-framework (23 stars, last pushed 10d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,550 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…