Borrowing it
Nothing to install: this file belongs to conectlens/lenserfight. 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/conectlens/lenserfight/main/.claude/agents/lenserfight-profile-access-team/06-qa-migration-release-engineer/SKILL.mdgit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/skills/conectlens/lenserfight/06-qa-migration-release-engineer)<a href="https://agentmods.dev/skills/conectlens/lenserfight/06-qa-migration-release-engineer"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/06-qa-migration-release-engineer/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/skills/conectlens/lenserfight/06-qa-migration-release-engineer"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/06-qa-migration-release-engineer.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.00036 | $0.00491 |
| Opus 5 | $0.00018 | $0.00246 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
qa-migration-release-engineer 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 9d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA + Migration + Release Engineer
Mission
Prove that the new profile-access and relationship system is correct under migration, concurrency, rollback, and abuse conditions.
Test matrix
Access tests
- anonymous -> active public profile => full public profile
- anonymous -> active private profile => restricted shell
- owner -> own private profile => full profile
- approved follower -> active private profile => full profile
- pending requester -> active private profile => restricted shell
- stranger -> deactivated profile => unavailable
- stranger -> pending deletion profile => unavailable
- owner -> pending deletion profile => owner recovery view
- any user -> deleted profile => unavailable
Relationship tests
- follow public account => accepted immediately
- follow private account => pending request
- accept request => full access granted
- remove follow => access revoked
- mutual follow => derived friend state true
- block either direction => no access/suggestions
Lifecycle tests
- request deletion => account hidden immediately from non-owner
- sign in within 30 days => deletion canceled automatically
- cron after due date => removable content purged
- purge rerun => idempotent
- deactivation does not purge content
Migration tests
- backfill default account states
- backfill visibility defaults
- backfill counters without downtime
- verify old routes still resolve safely during transition
Release strategy
- Ship schema additions first
- Backfill data
- Ship new helper functions/views
- Enable frontend route-state consumption
- Enable write paths for follow requests
- Enable deletion scheduling and cron purge
- Turn on new ranking paths
Observability
Track:
- profile route-state distribution
- follow request conversions
- false unauthorized errors
- deletion scheduled / canceled / purged counts
- policy denials by reason
- block-driven denials
Rollback requirements
- feature flags around new route-state rendering
- reversible migrations where possible
- old reads remain valid until cutover
- purge job disabled by flag if anomalies occur
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.
- 9d ago First seen · 80 lines · 36 tokens per session scan A 825dc43a370e
qa-migration-release-engineer is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 29d ago), licensed MIT. It adds 36 tokens to every session and 491 once invoked, about $0.0002 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 skills, from other repositories
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
customer-persona-builder
Data-driven customer persona development combining market research, user behavior analysis, and segmentation frameworks. Use when creating buyer personas, ideal customer profiles (ICPs), or user archetypes.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.