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 commands/kastheco/claude-plugins/setupgit clone --depth 1 https://github.com/kastheco/claude-pluginsWhat 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.00000 | $0.01643 |
| Opus 5 | $0.00000 | $0.00822 |
| Sonnet 5 | $0.00000 | $0.00329 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade B, and why
setup 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 yesterday.
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.
SETTINGS_FILE="$REPO_ROOT/.claude/settings.json" How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/kas:setup - Prepare Project for KAS Workflow
Validate prerequisites and verify the environment is ready.
Workflow
Execute these steps in order. Track results as PASS, FAIL (blocker), or WARN (non-blocking).
1. Check Prerequisites
Prerequisites are BLOCKERS - setup cannot continue if any fail.
1.1 Check GitHub CLI (gh)
# Check installed
if ! command -v gh &>/dev/null; then
echo "[FAIL] gh not found"
echo " Install: https://cli.github.com/"
# BLOCKER
fi
# Check version >= 2.0.0
GH_VERSION=$(gh --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
GH_MAJOR=$(echo "$GH_VERSION" | cut -d. -f1)
GH_MAJOR=${GH_MAJOR:-0}
if [[ "$GH_MAJOR" -lt 2 ]]; then
echo "[FAIL] gh version $GH_VERSION < 2.0.0"
echo " Upgrade: https://cli.github.com/"
# BLOCKER
fi
# Check authenticated
if ! gh auth status &>/dev/null; then
echo "[FAIL] gh not authenticated"
echo " Run: gh auth login"
# BLOCKER
fi
# Check repo scope
GH_SCOPES=$(gh auth status 2>&1 | grep -i "token scopes" || true)
if [[ -z "$GH_SCOPES" ]] || ! echo "$GH_SCOPES" | grep -qi "repo"; then
echo "[FAIL] gh missing 'repo' scope"
echo " Run: gh auth refresh -s repo"
# BLOCKER
else
echo "[PASS] gh $GH_VERSION (authenticated, repo scope)"
fi
1.2 Check Git Configuration
# Check version >= 2.20.0
GIT_VERSION=$(git --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
GIT_MAJOR=$(echo "$GIT_VERSION" | cut -d. -f1)
GIT_MINOR=$(echo "$GIT_VERSION" | cut -d. -f2)
GIT_MAJOR=${GIT_MAJOR:-0}
GIT_MINOR=${GIT_MINOR:-0}
if [[ "$GIT_MAJOR" -lt 2 ]] || [[ "$GIT_MAJOR" -eq 2 && "$GIT_MINOR" -lt 20 ]]; then
echo "[FAIL] git version $GIT_VERSION < 2.20.0"
# BLOCKER
fi
# Check user.name configured
GIT_NAME=$(git config --get user.name || true)
if [[ -z "$GIT_NAME" ]]; then
echo "[FAIL] git user.name not configured"
echo " Run: git config --global user.name \"Your Name\""
# BLOCKER
fi
# Check user.email configured
GIT_EMAIL=$(git config --get user.email || true)
if [[ -z "$GIT_EMAIL" ]]; then
echo "[FAIL] git user.email not configured"
echo " Run: git config --global user.email \"[email protected]\""
# BLOCKER
else
echo "[PASS] git $GIT_VERSION (user: $GIT_NAME <$GIT_EMAIL>)"
fi
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.
- yesterday First seen · 193 lines · 0 tokens per session scan B 28e52a5b8be9
setup is a command published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,643 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.