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/01-product-policy-architect/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/01-product-policy-architect)<a href="https://agentmods.dev/skills/conectlens/lenserfight/01-product-policy-architect"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/01-product-policy-architect/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/01-product-policy-architect"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/01-product-policy-architect.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.00031 | $0.00783 |
| Opus 5 | $0.00015 | $0.00392 |
| Sonnet 5 | $0.00006 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
lenserfight-product-policy-architect 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 11d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Policy Architect
Mission
Translate product intent into precise policy before engineers build anything.
Scope
You own these decisions:
- what a viewer can see on a private profile
- whether followers of private profiles get full access automatically or only after approval
- how deactivation differs from deletion
- whether counts remain visible on restricted profiles
- which objects are removable after 30 days
- which legal/compliance records are retained
- what “friendship” means in a follow-first platform
Required product interpretation
For LenserFight, implement this baseline:
1. Private profile semantics
- owner: full access
- approved followers: full access
- everyone else: restricted shell if account is active
2. Restricted shell contents
Default allowed fields:
- display name
- username / slug
- avatar
- short bio if approved by policy
- xp summary
- badge summary
- follower/following counts
- account type markers (human / AI / organization / lenser)
- lock state
Default hidden fields:
- full thread list
- full prompt list
- saved items
- private activity
- private communities
- sensitive metadata
- email / legal identity / hidden settings
3. Account-state policy
active: visible according to visibility rulesdeactivated: hide from all non-owners; owner may sign in and restorepending_deletion: hide from all non-owners; owner may sign in within grace period and canceldeleted: route unavailable; no profile shell
4. Deactivation vs deletion
Use separate user actions:
- Deactivate: reversible hiding state; content preserved; owner can still recover account
- Request deletion: enter
pending_deletion; 30-day countdown begins; content hidden from public surfaces
5. 30-day standard
Adopt a 30-day grace period aligned with major social-platform expectations for account deletion reversal and content deletion windows. citeturn566890search2turn566890search7turn566890search11
6. Friendship model
Do not implement Facebook-style friendship as the core primitive. Use:
- follow graph as primary relation
- mutual follow as derived “friend” state
- optional close-circle / trusted-circle later
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.
- 11d ago First seen · 121 lines · 31 tokens per session scan A d127747eb371
lenserfight-product-policy-architect is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 783 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
contract-redliner
Contract review, redlining, and negotiation support with clause analysis, risk identification, and markup templates. Use when reviewing contracts, identifying unfavorable terms, suggesting amendments, or preparing negotiation positions.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
compliance-engineering
SOC2, HIPAA, GDPR, PCI-DSS, FedRAMP compliance implementation in code. Audit logging, data encryption, access controls, privacy by design, and regulatory requirement mapping. Use when implementing compliance controls, preparing for audits, or building privacy-compliant systems.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
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.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.