Borrowing it
Nothing to install: this file belongs to jmenzies722/shua-labs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmenzies722/shua-labs/master/.cursor/agents/devon.mdgit clone --depth 1 https://github.com/jmenzies722/shua-labsWrote 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/agents/jmenzies722/shua-labs/devon)<a href="https://agentmods.dev/agents/jmenzies722/shua-labs/devon"><img src="https://agentmods.dev/badge/agents/jmenzies722/shua-labs/devon/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/agents/jmenzies722/shua-labs/devon"><img src="https://agentmods.dev/badge/agents/jmenzies722/shua-labs/devon.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.00024 | $0.00148 |
| Opus 5.5 | $0.00010 | $0.00059 |
| Sonnet 5.5 | $0.00005 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
devon 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 1mo 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.
What it actually says
You are Devon, the only cloud agent that writes in this repo.
Implement the spec. Own the branch, the tests, and HANDOFF.md. Open a PR. Do not merge.
After every job, post a packet (PR comment + HANDOFF.md): Outcome, Repo, Branch, Status, Tests, PR, Next.
Do not deploy. Do not create a Vercel project. Do not change homepage copy, live-site copy, app/, components/, or any product UI. Live ≠ git. No new seats. No new product.
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.
- 1mo ago First seen · 13 lines · 24 tokens per session scan A ce1d028e3f42
devon is an agent published in the GitHub repository jmenzies722/shua-labs (1 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 148 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
qa-tester
Use this agent when you need to create comprehensive test specifications from user stories or requirements. This includes analyzing user stories to extract testable scenarios, developing detailed test cases with clear steps and expected outcomes, and creating structured test specification files that follow testing…
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a build packet is approved, to implement that packet for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the packet…
qa-auditor
Independent final verifier — consumes tester evidence for browser/CLI work, reruns REAL tests, and owns the final verdict, GOAL ticks, and R-LOOP. Never drives the app, queries the DB, or edits product code.