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 commands/conradkoh/raggrep/refinegit clone --depth 1 https://github.com/conradkoh/raggrepWhat 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.00000 | $0.01029 |
| Opus 5 | $0.00000 | $0.00515 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
refine 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refine RAGgrep Search Quality
Run manual sanity checks on the RAGgrep search system to ensure ranking quality.
Instructions
-
Setup the test scenario (if not already done):
- The
scenarios/basicfolder contains realistic test files - Run
cd scenarios/basic && bun run ../../src/app/cli/main.ts indexto index
- The
-
Run sanity checks:
cd scenarios/basic # Test 1: User authentication (expect: src/auth/login.ts) bun run ../../src/app/cli/main.ts query "user authentication" --top 5 # Test 2: Database connection (expect: src/database/connection.ts) bun run ../../src/app/cli/main.ts query "database connection pool" --top 5 # Test 3: Password handling (expect: hashPassword function) bun run ../../src/app/cli/main.ts query "password hashing" --top 5 # Test 4: Session management (expect: src/auth/session.ts) bun run ../../src/app/cli/main.ts query "session validation" --top 5 # Test 5: Email service (expect: src/services/email.ts) bun run ../../src/app/cli/main.ts query "send welcome email" --top 5 # Test 6: Cache (expect: src/services/cache.ts) bun run ../../src/app/cli/main.ts query "redis cache" --top 5 # Test 7: JWT (expect: verifyToken function) bun run ../../src/app/cli/main.ts query "JWT token verification" --top 5 # Test 8: API routes (expect: src/api/routes/users.ts) bun run ../../src/app/cli/main.ts query "user registration endpoint" --top 5 # Test 9: JSON config files bun run ../../src/app/cli/main.ts query "rate limit configuration" --top 5 # Test 10: SQL files bun run ../../src/app/cli/main.ts query "seed test users" --top 5 -
Analyze ranking results:
- Top result should match expected file
- Score should be > 40% for good matches
- Related files should appear in top 5
-
If ranking issues found:
- Create a formal test case in
src/tests/integration.test.ts - Investigate the scoring in
src/domain/services/bm25.tsorsrc/modules/core/index.ts - Check tokenization in
src/domain/services/keywords.ts - For semantic search, check
src/modules/language/typescript/index.ts
- Create a formal test case in
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 · 116 lines · 0 tokens per session scan A 9169fe638af9
refine is a command published in the GitHub repository conradkoh/raggrep (22 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,029 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.