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 roedyrustam/vibes-plug --skill agentic-coding-workflow-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/agentic-coding-workflow-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/agentic-coding-workflow-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/agentic-coding-workflow-expert/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/roedyrustam/vibes-plug/agentic-coding-workflow-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/agentic-coding-workflow-expert.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.00110 | $0.02232 |
| Opus 5.5 | $0.00044 | $0.00893 |
| Sonnet 5.5 | $0.00022 | $0.00446 |
| Haiku 4.5 | $0.00011 | $0.00223 |
Grade A, and why
agentic-coding-workflow-expert 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 7d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Coding Workflow Expert
1. Agentic Code Generation Patterns / Pola Generasi Kode Agentic
Implement autonomous code generation workflows. Implementasikan workflow pembuatan kode otonom.
Core Patterns / Pola Inti:
- Single-file vs Multi-file Generation:
- Single-file: Isolate scope, update specific modules.
- Multi-file: Coordinate state across files, ensure API contract consistency.
- Context-Aware Completion: Query codebase knowledge graph for semantic context before generating.
- Ghost Text / Inline Suggestion: Provide real-time snippet integration paths.
- Plan → Implement → Verify → Refine: Always loop through planning, writing, testing, and iterating.
Code Example: Multi-file Generation Workflow
// workflow-generator.ts
interface GenerationTask {
plan: string;
files: string[];
}
class AgenticGenerator {
async execute(task: GenerationTask) {
console.log(`[PLAN] Executing: ${task.plan}`);
const generatedFiles = await this.generateFiles(task.files);
for (const file of generatedFiles) {
const isValid = await this.verify(file);
if (!isValid) {
await this.refine(file);
}
}
}
private async generateFiles(files: string[]) {
// Generate code with multi-file context awareness
return files.map(f => ({ name: f, content: "// generated code" }));
}
private async verify(file: any) {
// Run linter and tests
return true;
}
private async refine(file: any) {
// Apply fixes based on verification failures
}
}
2. Multi-Agent Code Swarms / Swarm Kode Multi-Agen
Coordinate multiple specialized agents for complex engineering tasks. Koordinasikan beberapa agen khusus untuk tugas rekayasa yang kompleks.
Swarm Architecture:
- Fan-out: Dispatch tasks to Frontend Agent, Backend Agent, Test Agent, and Review Agent.
- Shared Workspace: Utilize branched git worktrees for isolated, parallel development.
- Director Agent: Resolve conflicts, validate coherence across boundaries, merge branches.
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.
- 7d ago Changed 41fdbc7839bb
- 12d ago Changed 48eed0515b41
- 13d ago Changed 98b9c38ec1c5
- 15d ago Changed 35470953976e
- 16d ago Changed · -6 lines · +93 tokens per session c78a9b0ef86a
- 17d ago Changed · +11 lines · -93 tokens per session 365f2a8fd626
- 1mo ago First seen · 293 lines · 110 tokens per session scan A 690b1b4211a0
agentic-coding-workflow-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (75 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 2,232 once invoked, about $0.0004 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-09-14.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
spec-driven-eval
Scores how completely an implementation fulfills a PRD/spec, case by case, and produces a single comparable final grade. Invoke only when explicitly named (e.g. run spec-driven-eval); do not auto-trigger. Use when benchmarking spec-driven implementations, grading acceptance criteria, evaluating whether a feature was…
tlc-implement
Implement a work already planned: extracts a checklist, builds it, and proves every check with an independent verifier. Use when the user says "extract a checklist", "build this ticket", "implement this spec", or "tlc-implement". Do NOT use when nobody has decided what to build, or to design the work.
tlc-spec-lean
Spec-driven feature work that freezes obligations instead of the plan: one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors, then proof-backed checks, then build, then an independent Verifier. Use when the user says "tlc-spec-lean", "plan feature", "specify feature", "write the…
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions…