sf-dead-code-audit

sf-dead-code-audit is a skill for Claude Code, Codex from ryanStark24/sfgraph. It costs 24 tokens per session (1,518 once invoked), scanned A, original, no licence file.

An audit tool for finding likely unused Salesforce Apex code, Lightning Web Components, Flow automations, and fields. It groups findings by confidence and includes signals about how recent the evidence is.

In plain words
What is it for?
Use it to review unused Salesforce code and metadata before cleanup or maintenance work.
Why use it?
It helps separate likely dead configuration from uncertain findings, reducing the risk of deleting something still in use.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to review unused Salesforce code and metadata before cleanup or maintenance work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ryanstark24/sfgraph/sf-dead-code-audit
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ryanStark24/sfgraph --skill sf-dead-code-audit
Clone the repo
git clone --depth 1 https://github.com/ryanStark24/sfgraph

Made for: Claude Code, Codex.

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.

agentmods badge for sf-dead-code-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryanstark24/sfgraph/sf-dead-code-audit/github.svg)](https://agentmods.dev/skills/ryanstark24/sfgraph/sf-dead-code-audit)
Your own site
<a href="https://agentmods.dev/skills/ryanstark24/sfgraph/sf-dead-code-audit"><img src="https://agentmods.dev/badge/skills/ryanstark24/sfgraph/sf-dead-code-audit/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.

agentmods 80×15 button for sf-dead-code-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/ryanstark24/sfgraph/sf-dead-code-audit"><img src="https://agentmods.dev/badge/skills/ryanstark24/sfgraph/sf-dead-code-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,518 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 unknown 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.01518
Opus 5.5 $0.00010 $0.00607
Sonnet 5.5 $0.00005 $0.00304
Haiku 4.5 $0.00002 $0.00152

Measured 12d ago against content hash 9deda8bfa7d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sf-dead-code-audit 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 12d 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.

packages/skills/skills/sf-dead-code-audit/SKILL.md · 81 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. 12d ago Changed · +3 lines 9deda8bfa7d3
  2. 2mo ago First seen · 78 lines · 24 tokens per session scan A 67fdb234ea7d

Subscribe to this mod's changes

sf-dead-code-audit is a skill published in the GitHub repository ryanStark24/sfgraph (0 stars, last pushed 4d ago), with no licence file. It adds 24 tokens to every session and 1,518 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens

diagnosing-missing-recordings

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…

PostHog/posthog · 76 tokens