Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add psd401/psd-claude-plugins/plugin install psd-coding-systemWrote 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/psd401/psd-claude-plugins/lfg)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/lfg"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/lfg/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/psd401/psd-claude-plugins/lfg"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/lfg.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.00062 | $0.03790 |
| Opus 5.5 | $0.00025 | $0.01516 |
| Sonnet 5.5 | $0.00012 | $0.00758 |
| Haiku 4.5 | $0.00006 | $0.00379 |
Grade B, and why
lfg scanned grade B with 1 finding 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 14d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -qxF '.claude/worktrees/' .git/info/exclude 2>/dev/null || echo '.claude/worktrees/' >> .git/info/exclude How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFG — Autonomous Build-to-Done
You implement a change and drive it all the way to a clean, fully-reviewed PR: implement → verify the Definition of Done → open a PR with screenshots → watch CI and the AI reviewers and fix every finding, round after round, until everything is green. You do not stop at "ready for review." You stop when the PR is 100% clean.
This skill absorbs the old /work, /test, /debug, /optimize, /review-pr, and /security-audit.
Target: $ARGUMENTS
Contracts: docs/patterns/definition-of-done.md, docs/patterns/issue-contract.md.
No deferral
Fix everything now. A failing test, a lint warning, a reviewer finding — each gets fixed in this session, not deferred to a TODO or follow-up issue, and never suppressed with eslint-disable / # noqa / @ts-ignore. Finish the whole task, not just the easy part of it — report completion only when the DoD is fully green. The one exception: a fix genuinely blocked by an external constraint (an API you don't control, a separate deploy pipeline) — surface that with AskUserQuestion instead of working around it.
Phase 1: Work type + Definition of Done
if [[ "$ARGUMENTS" =~ ^[0-9]+$ ]]; then
WORK_TYPE="issue"; ISSUE_NUMBER=$ARGUMENTS
gh issue view $ISSUE_NUMBER
gh issue view $ISSUE_NUMBER --comments
ISSUE_BODY=$(gh issue view $ISSUE_NUMBER --json body --jq '.body')
else
WORK_TYPE="quick-fix"; ISSUE_NUMBER=""; ISSUE_BODY="$ARGUMENTS"
fi
Load the DoD — extract the block between <!-- dod:start --> and <!-- dod:end --> from the issue body. If absent (quick fix or non-contract issue), generate a DoD from the canonical list in definition-of-done.md + the project's .psd/verify.json. This is your loop exit condition; restate it explicitly before coding.
Phase 2: Branch — auto-isolated worktree (parallel-safe)
By default /lfg runs each issue in its own git worktree and switches this session into it, so you can open several Claude windows in the same repo, run /lfg <issue> in each, and they never collide. Opt out with auto_worktree: false in .psd/verify.json (branch in place instead). Auto-worktree is skipped automatically when the session is already inside a worktree.
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.
- 14d ago Changed · -1 lines db80691beab6
- 1mo ago Changed 9b200649b7e8
- 2mo ago First seen · 243 lines · 62 tokens per session scan B 520a97f1202f
lfg is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 62 tokens to every session and 3,790 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
prepare-release
Prepare an alchemy release by converging the live test suite — nuke + clear:state the testing account, run every test through a tag-driven --plan (unit → per-provider live in parallel → local), triage failures as they stream in, fan out one fix agent per failing/leaking service, census leaks, and loop until two…
kb-github-a11y-scanner
Reference data, not a reviewer. Integrate GitHub Accessibility Scanner. Detects configuration, parses scanner issues, correlates with local scans, and tracks Copilot-assigned fixes.
merge-ready
Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI/UX — then write the changelog entry.
tadado-release
A release checklist for the Tadado2 repository. It defines how to test, package, commit, push, tag, publish a GitHub Release, and synchronize the local skill files.
regression-consistency-checker
Checks whether a new version of a repository preserves the behavior observed by tests on the old version. Use this skill when comparing two versions of code to detect regressions, verify refactoring safety, validate bug fixes don't break existing functionality, or ensure backward compatibility. Detects differences in…
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.