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/defaultperson/agent-setup/publishnpx skills add DefaultPerson/agent-setup --skill publishgit clone --depth 1 https://github.com/DefaultPerson/agent-setupWhat 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.00050 | $0.01184 |
| Opus 5 | $0.00025 | $0.00592 |
| Sonnet 5 | $0.00010 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
publish 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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Remote: !
git remote -v 2>/dev/null || echo "No remote" - Branch: !
git branch --show-current 2>/dev/null || echo "Not a git repo" - GitHub repo: !
gh repo view --json nameWithOwner,visibility,description --jq '"\(.nameWithOwner) (\(.visibility)) — \(.description)"' 2>/dev/null || echo "Not on GitHub yet"
Interactive repo publication workflow. Uses gh CLI for everything.
Algorithm
-
Detect state:
git remote -v— check iforiginpoints to GitHub.- New repo (no origin): full creation flow (steps 2-13).
- Existing repo (origin exists): update flow — go to step 2 to review/update settings.
- No git repo:
git initfirst.
-
Ask questions (AskUserQuestion, single batch — all repos):
- Owner: personal account or organization? List available with
gh api user/orgs --jq '.[].login'+ personal account fromgh api user --jq .login. - Visibility: public / private / Keep current (existing repos only)
- Description: show auto-detected (from README.md or CLAUDE.md), ask to use or enter custom
- License: MIT (Recommended for public) / Apache-2.0 / GPL-3.0 / Keep current / None
- GitHub Pages: Yes (MkDocs Material) / No / Keep current
- Dependabot: Enable dependency updates? Yes / No / Keep current
- CI workflow: Set up GitHub Actions CI? Yes (auto-detect stack) / No / Keep current
.gitignore: Generate smart .gitignore? Yes (auto-detect stack + scan repo) / No / Keep current- README.md: Scaffold README if missing? Yes / No
- Owner: personal account or organization? List available with
-
Auto-detect (no user input needed):
- Repo name: from current directory name
- Topics: detect from stack files:
package.json→ nodejs, javascript/typescriptpyproject.toml/requirements.txt→ pythongo.mod→ golangCargo.toml→ rustDockerfile→ docker- Also infer from README content (keywords, frameworks)
- For existing repos: fetch current values with
gh repo view --json description,repositoryTopics,visibilityand show diff
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.
- 2d ago First seen · 102 lines · 50 tokens per session scan A 0f52bb8ad59d
publish is a skill published in the GitHub repository DefaultPerson/agent-setup (11 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,184 once invoked, about $0.0003 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
bark-notify-test
Send a Bark verification notification for the current Claude Code Bark setup on macOS or Windows. Use when the user wants to test delivery, confirm encryption works, or check whether the configured completion notification is healthy.
bark-notify
Use this skill whenever the user wants Claude Code to notify an iPhone through Bark when a task, turn, or coding session finishes. Works on macOS, Linux, and Windows. Trigger on requests about Bark notifications, Claude completion alerts, iPhone push reminders, completion messages, Bark hook setup, or Bark…
bark-notify-setup
Set up Bark completion notifications for Claude Code on macOS or Windows by safely writing the local Bark sender script and merging hooks into /.claude/settings.json. Use when the user explicitly asks to configure Bark for them or to directly install the completion notification flow.
bark-notify-uninstall
Remove Bark notification configuration from Claude Code on macOS, Linux, or Windows. Use when the user wants to uninstall, remove, or clean up Bark notifications, delete the Bark hook, or reset their Bark setup.
at-vision
Inspect screenshots, photos, diagrams, image paths, and image URLs when the task depends on visible content. Use when the prompt lacks actual image content, native inspection fails, or the user requests inspectimage; prefer the MCP tool, then the installed CLI.
webmcp-setup
Bootstraps webmcp-react into an existing React or Next.js app. Installs dependencies, adds WebMCPProvider, creates a first tool, and configures the MCP client bridge. Use when the user wants to set up WebMCP, add MCP tools to their app, integrate webmcp-react, or make their React app accessible to AI agents.