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 irahardianto/awesome-agv --skill workflow-sologit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/workflow-solo)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/workflow-solo"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/workflow-solo/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/irahardianto/awesome-agv/workflow-solo"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/workflow-solo.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.00032 | $0.01309 |
| Opus 5.5 | $0.00013 | $0.00524 |
| Sonnet 5.5 | $0.00006 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
workflow-solo 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Solo — Lean Feature Pipeline
Entry-point guard: This is a user-invoked command skill (
/workflow-solo). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Single-agent skill for feature development. Execute phases sequentially with complexity-appropriate depth.
- For multi-agent orchestration with parallel dispatch and review layers, use
/workflow-team. - Subagent spawning is a native capability — use it when beneficial, but this skill doesn't prescribe a multi-agent hierarchy.
Complexity Assessment
Assess the task on 3 dimensions before starting:
| Dimension | Low | High |
|---|---|---|
| Scope | 1–3 files, single module | 4+ files, cross-module |
| Risk | No breaking changes, internal only | Public API changes, data migrations |
| Knowledge | Familiar patterns exist in codebase | New technology, no precedent |
Route to a track:
| Track | When | Phases |
|---|---|---|
| Light | All dimensions Low | IMPLEMENT → VERIFY → COMMIT |
| Standard | Any dimension Medium/High | RESEARCH → IMPLEMENT → VERIFY → COMMIT |
| Thorough | Multiple dimensions High | RESEARCH → IMPLEMENT → VERIFY (full) → COMMIT |
Phase: RESEARCH
Track: Standard, Thorough only. Skip for Light.
Objective: Understand context, discover patterns, define scope.
- Load applicable idiom skill(s) per @code-idioms-and-conventions.md
- Search codebase for existing patterns per Pattern Discovery Protocol in @architectural-pattern.md
- Examine 3+ existing modules for consistency (>80% required)
- Search external documentation for unfamiliar technologies
- Create
task.mdwith atomic, testable tasks - Document findings in research artifact
- If a significant architecture decision is made, create an ADR using the
adrskill
Skills to consider: research-methodology, sequential-thinking, adr
Gate: Research artifact created. Task list defined. Patterns documented with >80% consistency.
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 · 140 lines · 32 tokens per session scan A 9d77b23ec6d4
workflow-solo is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 1,309 once invoked, about $0.0001 per session on Opus 5.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-10-15.
Other skills, from other repositories
common-git-collaboration
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
commit
Generate a conventional commit message for staged changes.
caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit.…
git
Git version control best practices: branching, commits, merging, conflict resolution, PR workflows. Use when managing branches, creating commits, merging code, or resolving conflicts.
change-hygiene
Version-control and change-flow discipline — commits, branches, pull requests, code review flow, and history that stays useful. Use when committing, branching, opening or reviewing PRs, resolving merge conflicts, planning how a big change lands, or when the user says "commit", "PR", "pull request", "branch strategy"…