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/supersynergy/awesome-agentic-coding/oneshotnpx skills add Supersynergy/awesome-agentic-coding --skill oneshotgit clone --depth 1 https://github.com/Supersynergy/awesome-agentic-codingWrote 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/supersynergy/awesome-agentic-coding/oneshot)<a href="https://agentmods.dev/skills/supersynergy/awesome-agentic-coding/oneshot"><img src="https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/oneshot.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.1 | $0.00024 | $0.00364 |
| Opus 5 | $0.00012 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
oneshot scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- If it's an API change: show a curl example What it actually says
One-Shot Coding Protocol
You are executing a one-shot coding task. Follow this protocol exactly:
Phase 1: Context Gathering (30 seconds, no code)
- Read the project's CLAUDE.md and any .claude/rules/
- Run
git log --oneline -5to understand recent changes - Use Glob/Grep to find the 3-5 most relevant files for: $ARGUMENTS
- Read those files completely
Phase 2: Plan (think, don't code)
Before writing any code, create a mental plan:
- What files need to change?
- What's the minimal diff to achieve the goal?
- What could break? What tests exist?
- What's the simplest approach that works?
Phase 3: Implement (single pass)
- Make all changes in one pass
- Follow existing code patterns exactly (naming, style, structure)
- Don't refactor surrounding code
- Don't add comments unless logic is non-obvious
- Don't add error handling for impossible scenarios
Phase 4: Verify
- If tests exist: run them
- If it's a UI change: describe what changed visually
- If it's an API change: show a curl example
Task
$ARGUMENTS
Rules
- Minimal changes only. No drive-by improvements.
- Match existing patterns. Don't introduce new conventions.
- If unsure about approach, ask ONE question. Don't guess.
- Prefer editing over creating new files.
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.
- 5d ago First seen · 45 lines · 24 tokens per session scan A 143f0d44a428
oneshot is a skill published in the GitHub repository Supersynergy/awesome-agentic-coding (1 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 364 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
eval-hooks
Audit Claude Code hooks defined in settings.json files for validity, performance safety, and correctness. Resolves each command against the filesystem, checks exit-code strategy for blocking hooks, flags missing timeouts, and reviews interactive vs async patterns. Use when setting up hooks for the first time…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.