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.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/commands/boparaiamrit/skills-by-amrit/quick)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/quick"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/quick/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/commands/boparaiamrit/skills-by-amrit/quick"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/quick.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.00023 | $0.00639 |
| Opus 5 | $0.00012 | $0.00319 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quick — Quick Task Execution
Execute a small, well-defined task without creating a full plan. For tasks that don't need phase structure.
When to Use
- Bug fixes that are clearly scoped
- Small features (< 30 min of work)
- Configuration changes
- Documentation updates
- One-off investigations
When NOT to Use (Use /plan + /execute Instead)
- Multi-file feature implementations
- Architectural changes
- Database migrations
- Anything touching authentication or authorization
- Changes requiring research first
Instructions
Step 1: Understand the Task
From $ARGUMENTS, determine:
- What needs to change? — Specific files and behavior
- Why? — The reason for the change
- Scope boundary — What is NOT included
Step 2: Quick Research
Spend 2-3 minutes understanding the context:
# Find relevant files
grep -rn "[keyword]" --include="*.ts" --include="*.js" --include="*.py" . | grep -v node_modules | head -20
# Read the main file
cat [relevant-file]
Understand existing patterns before writing code.
Step 3: Pre-Flight Check
git status --short
npm run build 2>&1 | tail -5
npm test 2>&1 | tail -5
Step 4: Implement
Follow these rules:
- Match existing patterns — Don't introduce new patterns for a quick task
- Minimal changes — Change the fewest lines possible
- No refactoring — If you see tech debt, note it but don't fix it
- Add tests — Even quick tasks should have tests if behavior changes
- Type safety — No
any, proper error handling
Step 5: Verify
npm run build 2>&1 | tail -5
npm test 2>&1 | tail -5
npm run lint 2>&1 | tail -5
Step 6: Summary
## Quick Task Complete
**Task:** [Description from $ARGUMENTS]
**Changes:**
- `path/to/file.ts` — [What changed]
- `path/to/test.ts` — [Test added]
**Verification:** Build ✅, Tests ✅, Lint ✅
**Next:** Run `/commit` to save these changes.
Step 7: Update State (If .planning/ Exists)
If .planning/STATE.md exists, append:
### Quick Task: [title]
- **Status:** ✅ Complete
- **Date:** [timestamp]
- **Files:** [list]
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 · 106 lines · 23 tokens per session scan A 7dc9f097b354
quick is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 639 once invoked, about $0.0001 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.