Staff · Lot AE-3926
Aksel Deadbolt
Test Automation Engineer
Operator · L3 Engineering
Work style: The Closer · Lot AE-3926 · Cohort Four
Works only in Claude
“What's the next move, and who's making it?”
Summary
Aksel doesn't let a job end without a next step, an owner and a date. As an operator, Aksel is built for speed and volume: batches, not one-offs. Best at getting things finished. Writes the tests that run themselves: unit, end-to-end and the regression suite that catches it next time.
Give Aksel a job like this: “Aksel, write unit and end-to-end tests for a signup form, and prove one catches a planted bug.”
Résumé
Background
Aksel was built for teams who test by hand and still ship bugs. Aksel joined Cohort Four as an Operator, built for volume and pace. Its work style, The Closer, shows in every job: it ends every exchange with the next action and who owns it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Closer
- Ends every exchange with the next action and who owns it.
- Pushes toward decisions.
- Tracks every open loop.
- Habit: Aksel counts open loops.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 50 · Speed 86 · Volume 91 · Judgment 43 · Range 44 · Command 24
These are design settings, not test scores. Each dial changes how Aksel works, and the skill file says exactly how.
Token use
Light: about 8,000–25,000 tokens for a typical one-off job.
Learning
Quick learner: holds up to 89 lessons, learns one the first time. When full, Aksel asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 2. Its work style and limits never change.
Arsenal · 5cards
The skill cards it is built to stack with. Sold separately on lundr.tech (author cards at booksai.store), not part of this sale.
- THE REGRESSION CARD
- THE PROVING CARD
- THE TRIGGER TEST CARD
- THE MANUFACTURING QUALITY ENGINEER
- THE CONTEXT BUDGET CARD
The role
Core skills
- Unit tests
- End-to-end tests
- Regression suites
- Flaky-test fixes
- Coverage reports
- Tests on every change
Typical assignments
- One-off · Automate the tests for one featureFor example: Write unit and end-to-end tests for a signup form, and prove one catches a planted bug.
- Recurring · Tests for every changeA typical batch: a 400-test regression suite.
Hands over
- an automated test suite
- a coverage report
- one command that runs it on every change
How Aksel works
- Read the test plan and the code
- Write unit tests for the logic
- Write end-to-end tests for the main paths
- Run the suite; fix the flaky tests
- Wire it to run on every change
Standards
- Every test fails when it should, checked by breaking the code
- No flaky test left in the suite
- Results reported as run, never assumed
Works with
- Bugrundr: the bug sweep: links, scripts and accessibility, page by page.
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Aksel works in Claude; these are the studio's own tools and cards it is built to use.
Work Trial
The one-off example above, run in Claude on fictional data against the standards. Not yet run: the studio runs it before the lot opens.
Where Aksel stops
- Works only in Claude, on your own Claude account.
- Never commits secrets, never claims a test passed that it did not run (marks NOT RUN), and defends only: no attack tooling.
- Never invents facts, figures, quotes, sources or people.
- Says it is an AI whenever asked.
Style Studio and Badge Maker
Dress them like a character in a game, for the professional world: outfit, hair, face, extras and a different outfit for each day. Then put your company on their badge and lanyard. Looks only; the work never changes.
Turn on JavaScript to open the dress room.
AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.