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/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/commands/proffesor-for-testing/agentic-qe/session)<a href="https://agentmods.dev/commands/proffesor-for-testing/agentic-qe/session"><img src="https://agentmods.dev/badge/commands/proffesor-for-testing/agentic-qe/session/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/commands/proffesor-for-testing/agentic-qe/session"><img src="https://agentmods.dev/badge/commands/proffesor-for-testing/agentic-qe/session.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.00000 | $0.01865 |
| Opus 5.5 | $0.00000 | $0.00746 |
| Sonnet 5.5 | $0.00000 | $0.00373 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
session 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 4d 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming Session Management
Complete guide to managing pair programming sessions.
Session Lifecycle
1. Initialization
claude-flow pair --start
2. Active Session
- Real-time collaboration
- Continuous verification
- Quality monitoring
- Role management
3. Completion
claude-flow pair --end
Session Commands
During an active session, use these commands:
Basic Commands
/help - Show all available commands
/status - Current session status
/metrics - View quality metrics
/pause - Pause current session
/resume - Resume paused session
/end - End current session
Code Commands
/explain - Explain current code
/suggest - Get improvement suggestions
/refactor - Refactor selected code
/optimize - Optimize for performance
/document - Add documentation
/comment - Add inline comments
Testing Commands
/test - Run test suite
/test-gen - Generate tests
/coverage - Check test coverage
/test-watch - Enable test watching
/mock - Generate mocks
Review Commands
/review - Full code review
/security - Security analysis
/perf - Performance review
/quality - Quality metrics
/lint - Run linters
Navigation Commands
/goto <file> - Navigate to file
/find <text> - Search in project
/recent - Recent files
/bookmark - Bookmark location
/history - Command history
Role Commands
/switch - Switch driver/navigator
/mode <type> - Change mode
/role - Show current role
/handoff - Prepare role handoff
Git Commands
/diff - Show changes
/commit - Commit with verification
/branch - Branch operations
/stash - Stash changes
/log - View git log
Session Status
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.
- 4d ago First seen · 407 lines · 0 tokens per session scan A d5b9cdc30737
session is a command published in the GitHub repository proffesor-for-testing/agentic-qe (501 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,865 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-10-11.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.