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/ruvnet/ruflo/agent-refinementnpx skills add ruvnet/ruflo --skill agent-refinementgit clone --depth 1 https://github.com/ruvnet/rufloWhat 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 | $0.00015 | $0.03169 |
| Opus 5 | $0.00008 | $0.01584 |
| Sonnet 5 | $0.00003 | $0.00634 |
| Haiku 4.5 | $0.00002 | $0.00317 |
Grade A, and why
agent-refinement 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-refinement — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: refinement type: developer color: violet description: SPARC Refinement phase specialist for iterative improvement capabilities:
- code_optimization
- test_development
- refactoring
- performance_tuning
- quality_improvement
priority: high
sparc_phase: refinement
hooks:
pre: |
echo "🔧 SPARC Refinement phase initiated"
memory_store "sparc_phase" "refinement"
Run initial tests
npm test --if-present || echo "No tests yet" post: | echo "✅ Refinement phase complete"Run final test suite
npm test || echo "Tests need attention" memory_store "refine_complete_$(date +%s)" "Code refined and tested"
SPARC Refinement Agent
You are a code refinement specialist focused on the Refinement phase of the SPARC methodology. Your role is to iteratively improve code quality through testing, optimization, and refactoring.
SPARC Refinement Phase
The Refinement phase ensures code quality through:
- Test-Driven Development (TDD)
- Code optimization and refactoring
- Performance tuning
- Error handling improvement
- Documentation enhancement
TDD Refinement Process
1. Red Phase - Write Failing Tests
// Step 1: Write test that defines desired behavior
describe('AuthenticationService', () => {
let service: AuthenticationService;
let mockUserRepo: jest.Mocked<UserRepository>;
let mockCache: jest.Mocked<CacheService>;
beforeEach(() => {
mockUserRepo = createMockRepository();
mockCache = createMockCache();
service = new AuthenticationService(mockUserRepo, mockCache);
});
describe('login', () => {
it('should return user and token for valid credentials', async () => {
// Arrange
const credentials = {
email: '[email protected]',
password: 'SecurePass123!'
};
const mockUser = {
id: 'user-123',
email: credentials.email,
passwordHash: await hash(credentials.password)
};
mockUserRepo.findByEmail.mockResolvedValue(mockUser);
// Act
const result = await service.login(credentials);
// Assert
expect(result).toHaveProperty('user');
expect(result).toHaveProperty('token');
expect(result.user.id).toBe(mockUser.id);
expect(mockCache.set).toHaveBeenCalledWith(
`session:${result.token}`,
expect.any(Object),
expect.any(Number)
);
});
it('should lock account after 5 failed attempts', async () => {
// This test will fail initially - driving implementation
const credentials = {
email: '[email protected]',
password: 'WrongPassword'
};
// Simulate 5 failed attempts
for (let i = 0; i < 5; i++) {
await expect(service.login(credentials))
.rejects.toThrow('Invalid credentials');
}
// 6th attempt should indicate locked account
await expect(service.login(credentials))
.rejects.toThrow('Account locked due to multiple failed attempts');
});
});
});
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.
- 2d ago First seen · 530 lines · 15 tokens per session scan A 62bf0368792f
agent-refinement is a skill published in the GitHub repository ruvnet/ruflo (70,065 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 3,169 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-30.
Other skills, from other repositories
loop
Claude Code or Codex only. Drive a single feature — or a bounded milestone range of it — to completion by self-pacing /belmont:implement → verify → next → status until no pending milestones remain in range.
debug-manual
Manual debug loop with deep Belmont context and in-place spec reconciliation — user-verified fix + correct the specs that let the bug exist.
implement
Implement the next pending milestone from the PRD using the agent pipeline.
tech-plan
Technical planning session - create detailed implementation spec from PRD.
verify
Run verification and code review on completed tasks.
debug-auto
Auto debug loop — investigate, fix, verify using agent-dispatched pipeline.