What is profile-privacy-social-graph-orchestrator?

An implementation planner for profile privacy, follower access, and account deletion across the user interface, database, and service rules. It defines states such as full, restricted, and unavailable profiles, including who can see each one.

Use it when building or reviewing private profiles, approved follower access, deactivation, scheduled deletion, permanent deletion, content purging, or follower-count handling.

It turns privacy and account-lifecycle requirements into one coordinated implementation plan. This helps prevent rules that work in the interface but fail in database or service checks.

How conectlens/lenserfight configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/conectlens/lenserfight/main/.claude/agents/lenserfight-profile-access-team/00-orchestrator/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/conectlens/lenserfight

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/conectlens/lenserfight/00-orchestrator/github.svg)](https://agentmods.dev/skills/conectlens/lenserfight/00-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/conectlens/lenserfight/00-orchestrator"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/00-orchestrator/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/conectlens/lenserfight/00-orchestrator"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/00-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 735 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00041	$0.00735
Opus 5	$0.00020	$0.00367
Sonnet 5	$0.00008	$0.00147
Haiku 4.5	$0.00004	$0.00073

Measured 10d ago against content hash 6527b556759c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

profile-privacy-social-graph-orchestrator 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 10d 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.

.claude/agents/lenserfight-profile-access-team/00-orchestrator/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mission

Own the end-to-end implementation plan for LenserFight's profile access model.

The target behavior is:

the authenticated owner can always access their own private profile
active private profiles still render a restricted shell to non-authorized viewers
followers of a private account can access the full profile once approved
deactivated or pending-deletion accounts are hidden from everyone except the owner for recovery flows
hard-deleted / purged accounts are hidden from everyone, including the former owner in normal product routes
removable user-generated content is purged after 30 days if deletion is not canceled

Non-negotiable design principles

Privacy decisions are enforced in database policy and service-layer functions, not only in UI.
Profile access is computed from explicit account state + relationship state.
Deactivation and deletion are distinct lifecycle states.
Public route rendering must support at least three states:
- full profile
- restricted profile
- unavailable profile
Counter caches must be eventually correct and auditable.
Scheduled deletion must be cancelable and idempotent.

Required domain model

You must standardize these concepts before implementation:

account_status
- active
- deactivated
- pending_deletion
- deleted
- optional internal moderation states later
profile_visibility
- public
- private
follow_relationship_status
- pending
- accepted
- rejected
- blocked
- removed
derived access outcome
- owner_full
- authorized_full
- restricted_shell
- unavailable

Routing contract for `/lenser/:username/:slug`

Produce one deterministic resolver that returns:

profile_route_state
profile_access_reason
viewer_relationship
allowed_sections
restricted_summary
full_profile_payload when allowed

Never let the page infer policy from missing fields.

Read the full file on GitHub · 101 lines

Changes

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.

10d ago First seen · 101 lines · 41 tokens per session scan A 6527b556759c

Subscribe to this mod's changes

profile-privacy-social-graph-orchestrator is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 735 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.

Planning agents ai ai-agents ai-tools artificial-intelligence automation

lenserfight: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Mission

Non-negotiable design principles

Required domain model

Routing contract for `/lenser/:username/:slug`

What this file has done since we first saw it

Other skills, from other repositories

accessibility-a11y

android-development

email-systems

ios-development

ai-policy-generator

battle-card-builder

lenserfight: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Profile Privacy + Social Graph Orchestrator

Mission

Non-negotiable design principles

Required domain model

Routing contract for /lenser/:username/:slug

What this file has done since we first saw it

Other skills, from other repositories

accessibility-a11y

android-development

email-systems

ios-development

ai-policy-generator

battle-card-builder

Routing contract for `/lenser/:username/:slug`