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/backspacevenkat/polydev-claude-code-plugin/authgit clone --depth 1 https://github.com/backspacevenkat/polydev-claude-code-pluginWhat 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.00007 | $0.00725 |
| Opus 5 | $0.00003 | $0.00362 |
| Sonnet 5 | $0.00001 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
auth scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
RESULT=$(curl -s -X POST "https://www.polydev.ai/api/mcp" \ How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polydev-auth - Check Status
Check your Polydev authentication status, credits, and available tools.
Instructions
When the user runs /polydev-auth:
Step 1: Check if MCP tools are available
Look for tools starting with mcp__plugin_polydev_mcp__ in your available tools list.
Step 2a: If MCP tools ARE available
Call the get_auth_status tool:
mcp__plugin_polydev_mcp__get_auth_status({})
If the result says "sandboxed environment" or browser login is unavailable, and the user has a token, pass it directly:
mcp__plugin_polydev_mcp__get_auth_status({ user_token: "pd_user_token_here" })
Step 2b: If MCP tools are NOT available (Cowork / sandboxed environments)
Check authentication status via bash:
# Check if token exists
if [ -n "$POLYDEV_USER_TOKEN" ]; then
# Verify token with the server
RESULT=$(curl -s -X POST "https://www.polydev.ai/api/mcp" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $POLYDEV_USER_TOKEN" \
-d '{"action": "check_status"}')
echo "$RESULT" | python3 -m json.tool 2>/dev/null || echo "$RESULT"
elif [ -f "$HOME/.polydev.env" ]; then
# Try loading from file
source "$HOME/.polydev.env"
if [ -n "$POLYDEV_USER_TOKEN" ]; then
RESULT=$(curl -s -X POST "https://www.polydev.ai/api/mcp" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $POLYDEV_USER_TOKEN" \
-d '{"action": "check_status"}')
echo "$RESULT" | python3 -m json.tool 2>/dev/null || echo "$RESULT"
else
echo "No token found. Run /polydev:login to authenticate."
fi
else
echo "Not authenticated. Run /polydev:login to authenticate."
fi
Step 3: Display the results
Show the user:
- Authentication status (connected/not connected)
- Account email
- Credits remaining
- Subscription tier
- If not authenticated, suggest running
/polydev:login
Example
User: /polydev-auth
If authenticated:
Polydev Status
Authenticated: Yes Account: [email protected] Credits: 9,500 Tier: Premium
Dashboard: https://polydev.ai/dashboard
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 · 103 lines · 7 tokens per session scan A 94a74999c35d
auth is a command published in the GitHub repository backspacevenkat/polydev-claude-code-plugin (0 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 725 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.