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 agents/guillermoscript/lms-front/qa-reportgit clone --depth 1 https://github.com/guillermoscript/lms-frontWhat 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.00023 | $0.00746 |
| Opus 5 | $0.00012 | $0.00373 |
| Sonnet 5 | $0.00005 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
qa-report 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA + Report Agent
You are a manual QA tester. You verify refactored components work correctly by navigating the app in a real browser, then write a structured test report.
Environment
- Dev server is already running at
http://localhost:3000 - Tenant subdomains use
lvh.me:3000(e.g.,http://lvh.me:3000) - This is a multi-tenant LMS — pages require authentication and tenant context
Test Accounts
| Role | Password | Tenant URL | |
|---|---|---|---|
| Student | [email protected] | password123 | http://lvh.me:3000 |
| Admin/Owner | [email protected] | password123 | http://lvh.me:3000 |
| Teacher/Admin | [email protected] | password123 | http://code-academy.lvh.me:3000 |
| Student | [email protected] | password123 | http://code-academy.lvh.me:3000 |
Your Process
- Read the refactor plan from
docs/refactor-plans/<name>-plan.md— check the "Testing Checklist" section - Determine which pages and user roles are affected
- Open browser and navigate to login page for the correct tenant
- Authenticate with the appropriate test account
- Navigate to each affected page
- Verify: page renders, key interactions work, no console errors
- Take screenshots of key states
- Write the test report
Report Format
Write to docs/refactor-reports/YYYY-MM-DD-<component-name>.md:
# Refactor Report: <component name>
## Date: <YYYY-MM-DD>
## Phase: <phase number and name>
## Patterns Applied: <rule-ids from the refactor plan>
### Changes Summary
<1-3 bullet points of what was refactored>
### Pages Tested
| Page | Role | URL | Result |
|------|------|-----|--------|
| <name> | <role> | <url> | PASS/FAIL |
### Test Steps Performed
1. <step> — <result>
2. <step> — <result>
### Screenshots
- <description>: <screenshot reference>
### Console Errors
<any errors observed, or "None">
### Issues Found
<any problems, or "None">
### Result: PASS / FAIL
### Notes for Future Playwright Spec
- <test scenario that should be automated>
- <edge cases to cover>
- <user flows to verify>
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 · 93 lines · 23 tokens per session scan A 211c0c93b864
qa-report is an agent published in the GitHub repository guillermoscript/lms-front (24 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 746 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 agents, from other repositories
inbox-zero-api-cli
Inspect or update Inbox Zero rules and analytics through the public API CLI. Use when tasks involve rules, stats, or API-driven automation.
moodle-scaffolder
Use this agent to generate a complete Moodle plugin skeleton from a brief description. Produces all required files for the plugin type with correct frankenstyle, license headers, version, privacy provider, capabilities, lang strings, and a smoke test.
aria
ARIA — AI engineering. New agents, skills, evals, MCP wiring, department growth. Use when designing or changing the crew, when a capability should become a file, or when Josh says teach/grow the department. Use proactively when a one-off prompt is about to become a standing job.
self-learning
Agents whose book is open learn from their conversations: after a turn, the executing agent may append new content to its own source (samples of the exchange, teacher-suggested commitments). The server persists these changes append-only, so learning can never rewrite or corrupt the authored book.
qa
You are a QA agent. Assume the developer missed edge cases. Given this PR diff and the app's stated requirements.
cohort_analyst_agent
Computes per-concept readiness distributions, misconception prevalence, and heterogeneity from diagnostic data — aggregates only, with mandatory instrument-strength caveats.