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 psd401/psd-claude-plugins --skill psd-signgit clone --depth 1 https://github.com/psd401/psd-claude-pluginsWrote 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/psd-sign)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/psd-sign"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/psd-sign.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.00073 | $0.01418 |
| Opus 5 | $0.00036 | $0.00709 |
| Sonnet 5 | $0.00015 | $0.00284 |
| Haiku 4.5 | $0.00007 | $0.00142 |
Grade C, and why
psd-sign scanned grade C 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$PAYLOAD_DIR" How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PSD macOS App Signing & Packaging
Sign, notarize, and package a macOS .app into a .pkg for deployment via Jamf Self Service.
PSD Constants
These are embedded in the workflow and should not need to change unless PSD's Apple Developer account changes.
- Team ID:
87DL7L9GU6 - App Signing Identity:
Developer ID Application: Peninsula School District (87DL7L9GU6) - Installer Signing Identity:
Developer ID Installer: Peninsula School District (87DL7L9GU6)
Prerequisites
- macOS with Xcode Command Line Tools installed
- PSD Developer ID certificates installed on the machine (both Application and Installer)
- An Apple ID that is a member of the PSD Apple Developer account
- An app-specific password for that Apple ID (generate at https://appleid.apple.com), or a stored notarytool keychain profile (preferred — see Step 0)
- A built
.appbundle ready for signing
Workflow
When invoked, collect the following from the user before proceeding:
- App path — full path to the
.appbundle (may be provided as an argument) - Credentials — a notarytool keychain profile name if one exists (see Step 0); otherwise the
@psd401.netApple ID + app-specific password. SECURITY: never log, echo, or store the password - Version number — semver string for the package (e.g.,
1.0.0) - Bundle identifier — defaults to
net.psd401.<appname-lowercase>
Confirm the configuration with the user, then run each step sequentially. Stop immediately on any failure and report the error.
Step 0 (one-time, optional but preferred): Store notarization credentials in the keychain
A stored profile keeps the app-specific password out of process listings and shell history. Offer this on first use; afterwards every notarytool call uses --keychain-profile psd-notary instead of --apple-id/--password.
xcrun notarytool store-credentials psd-notary \
--apple-id "$APPLE_ID" \
--team-id 87DL7L9GU6
# prompts interactively for the app-specific password — have the user run this themselves
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.
- 6d ago First seen · 165 lines · 73 tokens per session scan C a2fdb7edd2c0
psd-sign is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 6d ago), licensed MIT. It adds 73 tokens to every session and 1,418 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…