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/srstomp/pokayokay/quickgit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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.00009 | $0.00613 |
| Opus 5 | $0.00005 | $0.00307 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
quick 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Task Workflow
Create and immediately work on: $ARGUMENTS
DO NOT dispatch agents. DO NOT read skill references or subagent-dispatch docs. Work inline in this conversation.
When to Use
- Bug fixes not in the backlog
- Quick tweaks or improvements
- Support requests
- Small enhancements
- Any work that doesn't warrant full PRD planning
Steps
0. Discipline Gates
If the quick task changes behavior, use testing-strategy patterns and write
the test first. For bugs, use systematic-debugging before editing. Before
any "done", "fixed", or "passing" claim, use verification-before-completion
and cite the fresh command result.
1. Parse Task Description
From $ARGUMENTS, extract:
- Title: First sentence or phrase
- Type: Infer (bug, feature, chore)
- Priority: Default P2 unless urgent language detected
2. Create Task (if ohno available)
Use MCP mcp__ohno__create_task or:
npx @stevestomp/ohno-cli create "$TASK_TITLE" -t $TYPE
npx @stevestomp/ohno-cli start <task-id>
If ohno is not configured, skip task tracking and just do the work.
3. Complexity Check
Before starting, estimate scope. If the work will likely touch more than 3 files or require architectural decisions, stop and suggest:
"This looks complex enough for
/fix(bug) or/work(feature). Want to switch?"
If user says continue, proceed inline.
4. Work Inline
Do the work directly. Follow this checklist:
- Write a test first if behavior is changing
- For bug fixes: reproduce and document root cause before editing
- Implement the change
- Run fresh verification commands and read the output
- Self-review the diff (
git diff) — is it minimal and correct? - No scope creep — only do what was asked
- Commit with conventional message
5. Complete Task
If ohno task was created:
npx @stevestomp/ohno-cli done <task-id> --notes "What was done"
Output
## Quick Task Done
**Task**: [task-id or "untracked"] - [title]
**Files Changed**: [list]
**Test**: [test added/updated or "no behavior change"]
**Commit**: [hash] [message]
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 · 81 lines · 9 tokens per session scan A da5d6346686b
quick is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 613 once invoked, about $0.0000 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.