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/pcatattacks/solopreneur-plugin/helpnpx skills add pcatattacks/solopreneur-plugin --skill helpgit clone --depth 1 https://github.com/pcatattacks/solopreneur-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.00041 | $0.02136 |
| Opus 5 | $0.00020 | $0.01068 |
| Sonnet 5 | $0.00008 | $0.00427 |
| Haiku 4.5 | $0.00004 | $0.00214 |
Grade A, and why
help 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 164 lines · 41 tokens per session scan A 94965e981675
help is a skill published in the GitHub repository pcatattacks/solopreneur-plugin (14 stars, last pushed 4mo ago), with no licence file. It adds 41 tokens to every session and 2,136 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
goal-loop
Loop engineering as gradient descent — a guided goal loop where an agent factory generates goal-specialized agents (implementer, verifier, diagnoser, judge) and iterates forward → loss → backward → update until the goal is provably met. Evidence is split into visible validation (the implementer's loss) and held-out…
metaprompt
Generate a complete, ready-to-use prompt for a target model and harness. Triggers: metaprompt, generate a prompt for, write me a prompt, create a system prompt, prompt engineer this, optimize this prompt.
codex-judge
Cross-provider LLM judge using Codex (GPT-5) to evaluate implementations written by Claude. Internal skill invoked by the insistir lead during the review loop. Not user-facing.
constatar-verify
Run and interpret verification through the constatar engine — the 6-rung ladder, grounded evidence, and conformance auditing. Use when the user asks to verify work with constatar, run a constatar plan, or audit a constatar run.
file-todos
File-based TODO lifecycle for tracking review findings, managing technical debt, and organizing work items. Each TODO is a standalone markdown file with YAML frontmatter, named by convention: {id}-{status}-{priority}-{description}.md. Status transitions drive the lifecycle: pending (created from review) -> ready…
constatar-plan
Author plan.toml files for the constatar engine — units, dependencies, adapters, and verification plans per the 6-rung ladder. Use when the user wants to plan or orchestrate multi-agent work with constatar.