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 DailybotHQ/deepworkplan-skill --skill shellcheck-fixgit clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skillWrote 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/dailybothq/deepworkplan-skill/shellcheck-fix)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/shellcheck-fix"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/shellcheck-fix/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.
<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/shellcheck-fix"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/shellcheck-fix.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00406 |
| Opus 5.5 | $0.00014 | $0.00162 |
| Sonnet 5.5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
shellcheck-fix 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 1mo 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
Shellcheck Fix
Goal
Keep setup.sh, skills/deepworkplan/shared/context.sh, and scripts/*.sh
shellcheck-clean and runnable on macOS's default bash 3.2.
When to use
After editing any shell script, or when CI's shellcheck step fails.
Steps
- Run
shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh. - Fix each finding. When resolving, keep the script bash 3.2-safe:
- replace
mapfile/readarraywithwhile IFS= read -r line; do …; done < <(cmd) - replace
declare -Awith a restructured approach - replace
${var^^}/${var,,}withtr '[:lower:]' '[:upper:]'
- replace
- Confirm each script starts with
#!/usr/bin/env bashthenset -euo pipefail. - Re-run shellcheck until clean.
- If
setup.shchanged, smoke-test it:HOME="$(mktemp -d)" ./setup.sh --host claude.
Validation
shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh exits 0,
and the installer smoke test still creates the expected symlinks.
Notes
Do not change setup.sh public flags (--host, --help) or symlink names
without flagging a MAJOR bump. CI runs the smoke job on Ubuntu and macOS.
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.
- 1mo ago First seen · 41 lines · 35 tokens per session scan A cfdff200123a
shellcheck-fix is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 406 once invoked, about $0.0001 per session on Opus 5.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
gsd-debug
Systematic debugging with persistent state across context resets.
gsd-forensics
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
kiro-debug
Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
gsd-ns-review
quality gates | code review debug audit security eval ui.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.