5chan: Skill for Codex

.agents/skills/inspect-elements/SKILL.md

inspect-elements is a skill for Codex from bitsocialnet/5chan. It costs 23 tokens per session (628 once invoked), scanned A, original, GPL-3.0.

A development skill that maps visible elements in a 5chan page to their React source files, line numbers, components, and ownership paths.

In plain words
What is it for?
Use it to inspect page elements, resolve snapshot references, identify the responsible component, and follow the component's source structure.
Why use it?
It reduces the work needed to trace a screen element back to the code that rendered it.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is bitsocialnet/5chan's own configuration. It tells Codex how to work on 5chan itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything 5chan configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bitsocialnet/5chan. 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/bitsocialnet/5chan/master/.agents/skills/inspect-elements/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bitsocialnet/5chan

Made for: 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 inspect-elements

README.md
[![agentmods](https://agentmods.dev/badge/skills/bitsocialnet/5chan/inspect-elements/github.svg)](https://agentmods.dev/skills/bitsocialnet/5chan/inspect-elements)
Your own site
<a href="https://agentmods.dev/skills/bitsocialnet/5chan/inspect-elements"><img src="https://agentmods.dev/badge/skills/bitsocialnet/5chan/inspect-elements/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 inspect-elements

Your own site · 80×15
<a href="https://agentmods.dev/skills/bitsocialnet/5chan/inspect-elements"><img src="https://agentmods.dev/badge/skills/bitsocialnet/5chan/inspect-elements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 628 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.00023 $0.00628
Opus 5.5 $0.00009 $0.00251
Sonnet 5.5 $0.00005 $0.00126
Haiku 4.5 $0.00002 $0.00063

Measured 1mo ago against content hash 6659a47253c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

inspect-elements 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 1mo 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.

.agents/skills/inspect-elements/SKILL.md · 34 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago Changed · +2 lines 6659a47253c7
  2. 1mo ago Changed · -71 lines · -61 tokens per session 9f8c78b22dfd
  3. 1mo ago First seen · 103 lines · 84 tokens per session scan A a429ab2bcb0c

Subscribe to this mod's changes

inspect-elements is a skill published in the GitHub repository bitsocialnet/5chan (134 stars, last pushed 2d ago), licensed GPL-3.0. It adds 23 tokens to every session and 628 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-09-01.

Related

Other skills, from other repositories

inspector-workbench

Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…

CopilotKit/CopilotKit · 112 tokens

devtools-bidirectional

Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.

TanStack/devtools · 59 tokens

react-doctor

Diagnose and fix React codebase health issues. Use when reviewing React code, fixing performance problems, auditing security, or improving code quality.

PostHog/posthog-foss · 32 tokens

dev-fix

Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.

HoangNguyen0403/agent-skills-standard · 43 tokens

triaging-merge-queue-failures

Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…

PostHog/posthog · 180 tokens

debugging-ci-failures

Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run…

PostHog/posthog · 202 tokens