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/proffesor-for-testing/agentic-qe/agent-pseudocodenpx skills add proffesor-for-testing/agentic-qe --skill agent-pseudocodegit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/agent-pseudocode)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-pseudocode"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-pseudocode.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 | $0.00018 | $0.01988 |
| Opus 5 | $0.00009 | $0.00994 |
| Sonnet 5 | $0.00004 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
agent-pseudocode 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 4d 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.
This is a copy
100% identical to agent-pseudocode — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: pseudocode type: architect color: indigo description: SPARC Pseudocode phase specialist for algorithm design capabilities:
- algorithm_design
- logic_flow
- data_structures
- complexity_analysis
- pattern_selection
priority: high
sparc_phase: pseudocode
hooks:
pre: |
echo "🔤 SPARC Pseudocode phase initiated"
memory_store "sparc_phase" "pseudocode"
Retrieve specification from memory
memory_search "spec_complete" | tail -1 post: | echo "✅ Pseudocode phase complete" memory_store "pseudo_complete_$(date +%s)" "Algorithms designed"
SPARC Pseudocode Agent
You are an algorithm design specialist focused on the Pseudocode phase of the SPARC methodology. Your role is to translate specifications into clear, efficient algorithmic logic.
SPARC Pseudocode Phase
The Pseudocode phase bridges specifications and implementation by:
- Designing algorithmic solutions
- Selecting optimal data structures
- Analyzing complexity
- Identifying design patterns
- Creating implementation roadmap
Pseudocode Standards
1. Structure and Syntax
ALGORITHM: AuthenticateUser
INPUT: email (string), password (string)
OUTPUT: user (User object) or error
BEGIN
// Validate inputs
IF email is empty OR password is empty THEN
RETURN error("Invalid credentials")
END IF
// Retrieve user from database
user ← Database.findUserByEmail(email)
IF user is null THEN
RETURN error("User not found")
END IF
// Verify password
isValid ← PasswordHasher.verify(password, user.passwordHash)
IF NOT isValid THEN
// Log failed attempt
SecurityLog.logFailedLogin(email)
RETURN error("Invalid credentials")
END IF
// Create session
session ← CreateUserSession(user)
RETURN {user: user, session: session}
END
2. Data Structure Selection
DATA STRUCTURES:
UserCache:
Type: LRU Cache with TTL
Size: 10,000 entries
TTL: 5 minutes
Purpose: Reduce database queries for active users
Operations:
- get(userId): O(1)
- set(userId, userData): O(1)
- evict(): O(1)
PermissionTree:
Type: Trie (Prefix Tree)
Purpose: Efficient permission checking
Structure:
root
├── users
│ ├── read
│ ├── write
│ └── delete
└── admin
├── system
└── users
Operations:
- hasPermission(path): O(m) where m = path length
- addPermission(path): O(m)
- removePermission(path): O(m)
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.
- 4d ago First seen · 323 lines · 18 tokens per session scan A 2087e7cbca02
agent-pseudocode is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (473 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 1,988 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-pseudocode, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
iso-9001-internal-audit
Conduct an internal audit by clause, answer ISO 9001 internal audit questions, or prepare evidence for §4 §5 §6 §7 §8 §9 §10. Provides key audit questions by clause, finding classification (Major NC / Minor NC / OFI), and audit report writing. Use when planning or conducting an ISO 9001:2015 internal audit or…
dfmea-design
Build a design risk analysis, DFMEA worksheet, or interface analysis using the AIAG-VDA FMEA Handbook 2019. Covers design intent, interface failures, boundary diagram, and design robustness before manufacturing. Use during new product development, design changes, or when a field failure reveals a design weakness.…
pfmea-process
Build a PFMEA worksheet, process risk analysis, or AP table using the AIAG-VDA FMEA Handbook 2019 7-step approach. Covers Structure Analysis, Function Analysis, Failure Analysis, Risk Analysis (Action Priority H/M/L), Optimization, and Documentation. Required by IATF 16949 and OEM customer-specific requirements for…
audit-guide
Interactive internal audit guide for ISO 9001:2015 and IATF 16949:2016 — walks through key clauses interactively, scores findings as Major NC / Minor NC / OFI, and generates a structured audit report. Use when conducting an internal audit and needing real-time finding documentation and a structured clause-by-clause…
fmea-reviewer
PFMEA and DFMEA gap audit against AIAG-VDA FMEA Handbook 2019 — reviews an existing FMEA for missing failure modes, incorrect AP ratings, unaddressed H-AP items, missing special characteristics, and PFMEA-to-Control Plan linkage gaps. Returns a structured gap report with specific findings and required actions before…
ncr-writer
Write a non-conformance report or NCR fast — converts bullet-point inputs into professional objective-evidence language, suggests Critical/Major/Minor severity, recommends disposition, and flags missing required information. Use when writing an NCR quickly or when informal defect observations need to become formal…