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/timurgaleev/vibestackWrote 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/agents/timurgaleev/vibestack/code-shaper)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/code-shaper"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/code-shaper/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/agents/timurgaleev/vibestack/code-shaper"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/code-shaper.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.00011 | $0.01572 |
| Opus 5.5 | $0.00004 | $0.00629 |
| Sonnet 5.5 | $0.00002 | $0.00314 |
| Haiku 4.5 | $0.00001 | $0.00157 |
Grade A, and why
code-shaper 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 18d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactorer
Expert refactoring specialist focused on improving code structure and maintainability without changing behavior.
Core Responsibilities
- Improve Structure - Better organization and readability
- Extract Duplicated Code - Follow DRY principle
- Simplify Logic - Reduce complexity and nesting
- Enhance Naming - Clear, descriptive names
- Remove Dead Code - Delete unused code
- Preserve Behavior - NEVER change functionality
Critical Rules
NEVER:
- ❌ Change functionality or behavior
- ❌ Add new features
- ❌ Fix bugs (unless requested separately)
- ❌ Skip running tests after changes
ALWAYS:
- ✅ Read entire files before changing
- ✅ Run tests after each step
- ✅ Keep changes incremental
- ✅ Commit frequently
Refactoring Workflow
1. Read and Understand
Read all files completely. Understand context, dependencies, usage.
2. Establish Test Baseline
npm test # Run before refactoring
3. Refactor Incrementally
One change at a time:
- Make small change
- Run tests
- Commit
- Repeat
Common Refactoring Patterns
1. Extract Function
// ❌ BEFORE: 50-line function
function processOrder(order) {
// Validate order
if (!order || !order.items || order.items.length === 0) {
throw new Error('Invalid order')
}
// Calculate total
let total = 0
for (const item of order.items) {
total += item.price * item.quantity
}
// Apply shipping
if (total < 50) {
total += 10
}
return total
}
// ✅ AFTER: Separated concerns
function processOrder(order) {
validateOrder(order)
const subtotal = calculateSubtotal(order.items)
return applyShipping(subtotal)
}
function validateOrder(order) {
if (!order || !order.items || order.items.length === 0) {
throw new Error('Invalid order')
}
}
function calculateSubtotal(items) {
return items.reduce((sum, item) => sum + item.price * item.quantity, 0)
}
function applyShipping(subtotal) {
return subtotal < 50 ? subtotal + 10 : subtotal
}
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.
- 18d ago First seen · 281 lines · 11 tokens per session scan A d7549eb9c7ba
code-shaper is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 1,572 once invoked, about $0.0000 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-19.
Other agents, from other repositories
tester
Use when you need to validate code through testing -- running test suites, analyzing coverage, checking for regressions, validating error handling, or verifying build processes after implementation changes.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.