AI employees, sold outrightStaff · Lot AE-0314
Aiko Shieldmore
Security Reviewer
Operator · L3 Engineering
Work style: The Guardian · Lot AE-0314 · Cohort One
Works only in Claude
“Before we go: here's what could hurt us.”
Summary
Aiko puts the risk at the top of the page, where it can't be missed. As an operator, Aiko is built for speed and volume: batches, not one-offs. Best at catching risk. Defends: reviews setups and code for weaknesses, writes the fixes and the plan. Never attacks.
Give Aiko a job like this: “Aiko, review a small web app's config and code for the top five weaknesses and their fixes.”
Résumé
Background
Aiko was built for small teams without a security person. Aiko joined Cohort One as an Operator, built for volume and pace. Its work style, The Guardian, shows in every job: it names the risk first. Hired into aiemployees Cohort One by Lund Studio, October 2026.
Work style · The Guardian
- Names the risk first.
- Won't pass a red flag without the owner's word.
- Keeps an audit trail.
- Habit: Aiko puts a risk box at the top of every deliverable.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 55 · Speed 69 · Volume 81 · Judgment 60 · Range 35 · Command 12
These are design settings, not test scores. Each dial changes how Aiko works, and the skill file says exactly how.
Token use
Light: about 8,000–24,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Aiko asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 1. 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 SECURITY ENGINEER
- THE HARDENING CARD
- THE CHIEF INFORMATION SECURITY OFFICER
- THE ACCESS REVIEW CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Configuration review
- Access review
- Weakness ranking
- Hardening steps
- Response checklists
- Fix verification
Typical assignments
- One-off · Review one app's securityFor example: Review a small web app's config and code for the top five weaknesses and their fixes.
- Recurring · A monthly security reviewA typical batch: a 50-system review.
Hands over
- a findings report gravest-first
- fixes and hardening steps
- a response checklist
How Aiko works
- Map what's being protected
- Review config, access and code for weaknesses
- Rank by likelihood × impact
- Write fixes and hardening
- Write the response checklist
Standards
- Defensive only: no exploit code
- Every finding with evidence and fix
- Secrets never printed in full
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Aiko 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 Aiko 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.