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 skills add J-Pster/Psters_AI_Workflow --skill using-psters-workflowgit clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/using-psters-workflow)<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/using-psters-workflow"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/using-psters-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/using-psters-workflow"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/using-psters-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00368 |
| Opus 5 | $0.00017 | $0.00184 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
using-psters-workflow 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 9d 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.
What it actually says
Using Psters Workflow (Meta-Skill)
Use this skill to decide which workflow skill must be applied before responding or implementing.
Rule
If there is even a small chance a workflow skill applies, invoke it first.
Extremely important
If there is a 1% chance a skill is relevant, use it. No rationalization. No skipping because task looks "simple".
Priority order
- Process discipline skills:
systematic-debuggingverification-before-completion
- Execution-context skills:
git-worktreefinishing-a-development-branchorchestrating-multi-agents
- Domain/convention skills:
nestjs-conventionsangular-conventionsaws-lambda-deploycommit-changes
Red flags
- Acting immediately without choosing a skill path.
- Declaring completion before verification.
- Proposing bug fixes before root-cause analysis.
- Closing worktree/branch ad hoc without a finishing checklist.
- "I will quickly check files first."
- "This does not need a skill."
- "I remember the skill, no need to read."
Quick routing
- Bug or failing behavior ->
systematic-debugging - End of implementation ->
verification-before-completion - Need isolated parallel branch ->
git-worktree - Need explicit multi-subagent parallelization ->
orchestrating-multi-agents - Work finished and branch decision needed ->
finishing-a-development-branch
When uncertain, prefer discipline over speed.
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.
- 9d ago First seen · 53 lines · 34 tokens per session scan A bc899af683dd
using-psters-workflow is a skill published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 368 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-30.
Other skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
An index of programming guidance for Python, Go, Rust, TypeScript, Java, C++, and shell scripting.
tencent-docs
A Tencent Docs assistant for creating, reading, editing, organizing, importing, and exporting online documents, spreadsheets, presentations, diagrams, and forms.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
wechat-article-pro
A WeChat public-account publishing assistant that searches for current topics, writes long-form articles, creates a cover image, and formats the result for publishing.
wechat-search
Search WeChat Official Account articles using OpenClaw's web search, Tavily API, and web fetch capabilities with compliance-focused design.