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 skills add grasscaograss/AwesomeWeldoneSkills --skill weld-plan-debuggit clone --depth 1 https://github.com/grasscaograss/AwesomeWeldoneSkillsWrote 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/grasscaograss/awesomeweldoneskills/weld-plan-debug)<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/weld-plan-debug"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/weld-plan-debug.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.1 | $0.00093 | $0.02643 |
| Opus 5 | $0.00046 | $0.01321 |
| Sonnet 5 | $0.00019 | $0.00529 |
| Haiku 4.5 | $0.00009 | $0.00264 |
Grade A, and why
weld-plan-debug 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 7d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weld Planning Debug Workflow
1. Prerequisite Checks
Before investigating, confirm the following are available:
- Stack trace or error log from the user (production log, simulation log, or pasted exception).
- Key source files exist in the current working tree:
src/Robim.Devices.Robot/Plan/Solver/RobotPlanSolver.cs— solver core, throwsSolvePath Failed!src/Weldone.Application/Plan/PlanManager.DualArm.cs— dual-arm transition planningsrc/Weldone.Application/Robot/ExternalRobotAppService.cs— external axis pre-planningsrc/Weldone.Domain/WorkpieceManager/WorkpieceManagerBase.cs— seam group parsingsrc/Weldone.Application/Plan/SolveStrategy/DualArmStrategy.cs— dual-arm param builder
- ILogger instance is accessible in the failing class (verify
using Microsoft.Extensions.Logging;). - OpenSpec spec for the feature area exists under
openspec/specs/oropenspec/changes/(check for intended behavior).
If the user only says "planning failed" without a stack trace, ask for the log first.
2. Step-by-Step Procedure
Step 1 — Anchor on the stack trace (30 seconds)
- Read the error message the user pasted.
- Identify the topmost method name and line number in the Weldone/Robim namespace.
- Formulate a 2-sentence hypothesis about what went wrong and where.
Step 2 — Read the failing site and its caller (2 files max)
Readthe method at the line number from the stack trace.Readthe immediate caller one level up.- If the root cause is not obvious,
Grepfor the method name to find all call sites. - Stop here if unclear. Ask the user: "Hypothesis: [X]. I need to check [Y] to confirm. Proceed?"
Step 3 — Inspect planning parameters and state
Planning failures are almost always param/state mismatches. Check:
ExSearchTimesvalue and who last set it (DualArmStrategysets 50,DualArmTransitionWithAirWallPlanStrategysets 1, default is 1).LastJointPos/_armJointPosesstate — is it stale or mutated between seams?fixedIndicesandboundariesconsistency (for external axis planning).- Shared cache dictionaries (
ScanTransCaches,WeldTransCaches,ExternalCache) — are they cleared between planning runs?
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.
- 7d ago First seen · 154 lines · 93 tokens per session scan A 884e7e5fd9d6
weld-plan-debug is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 93 tokens to every session and 2,643 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.