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/eladariel/pseudo-code-prompting-plugin/transformgit clone --depth 1 https://github.com/EladAriel/pseudo-code-prompting-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.00030 | $0.00923 |
| Opus 5 | $0.00015 | $0.00462 |
| Sonnet 5 | $0.00006 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
Transform Requirements to Pseudo-Code 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 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.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transform Requirements to Pseudo-Code
This command runs a 6-step pipeline:
- Detect Tech Stack - Identifies your project type (Node.js, Python, Go, Rust, Java)
- Compress (if needed) - Auto-compresses verbose requirements to 80% while preserving technical details
- Transform to Pseudo-Code - Converts natural language to PROMPTCONVERTER-style function notation
- Validate Completeness - Checks for missing security, error handling, timeouts, logging
- Optimize - Adds standard parameters (timeouts, retry logic, error mappings, logging)
- Bridge to cc10x - Saves pseudo-code to specification and offers TDD integration
Usage
Simply say:
Transform to pseudocode: Add OAuth with Google and GitHub providers. Users should be able to log in via OAuth, have tokens automatically refresh, be logged out after 24 hours, and get rate limited to 10 login attempts per hour.
What You Get
✓ Production-ready pseudo-code with all parameters specified ✓ Architecture-aware file paths for your tech stack ✓ Complete error handling defined ✓ Security requirements called out ✓ Timeouts, retry logic, caching all included ✓ Option to auto-inject into cc10x for TDD workflow
Output Example
implement_oauth_authentication(
providers=["google", "github"],
token_type="jwt",
access_token_ttl="15m",
refresh_token_enabled=true,
session_timeout="24h",
rate_limiting={
"login_attempts": "10/1h",
"token_refresh": "30/1h"
},
target_files=["src/auth/oauth.ts", "src/auth/strategies/", "src/middlewares/auth.ts"],
error_handling={
"invalid_provider": 400,
"invalid_code": 400,
"token_expired": 401,
"invalid_refresh_token": 401,
"insufficient_scope": 403
},
security={
"validate_redirect_uri": true,
"use_pkce": true,
"secure_cookie": true,
"http_only": true,
"same_site": "strict"
},
validation={
"validate_email_format": true,
"validate_provider_response": true
},
logging={
"log_login_attempts": true,
"log_token_operations": true,
"log_errors": true
},
timeout="5s",
retry={"max_attempts": 3, "backoff": "exponential"},
cache={"ttl": "5m", "key": "oauth_state"}
)
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 · 107 lines · 30 tokens per session scan A 3735bce73d1a
Transform Requirements to Pseudo-Code is a command published in the GitHub repository EladAriel/pseudo-code-prompting-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 923 once invoked, about $0.0002 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-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.