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/proffesor-for-testing/agentic-qe/agent-refinementnpx skills add proffesor-for-testing/agentic-qe --skill agent-refinementgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/agent-refinement)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-refinement"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-refinement.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 | $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 yesterday.
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.
This is a copy
100% identical to agent-refinement — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- yesterday First seen · 530 lines · 15 tokens per session scan A 62bf0368792f
agent-refinement is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (474 stars, last pushed 3d ago), 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. It is 100% identical to agent-refinement, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
create-tooluniverse-skill
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
test
Write/run tests, check coverage, or TDD discipline. Triggers "test", "write tests", "add tests", "run tests", "coverage", "unit test", "integration test", "TDD", "test-first", "red-green-refactor", "bugs-that-must-not-recur"; post-implementation, pre-merge.