agentleFS
o1xhacko1xhack/CodexBar-Mobile/.agents/skills/codexbar/SKILL.md

codexbar

Skill76 starsChanged 15 days agoMITView on GitHub

CodexBar read. Provider usage, limits, credits, config health. JSON. No writes.

5 other projects use a version of this; 1 new project in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 2

    1. steipete/CodexBar★ 23k100% same
    2. Richard-Yang0130/vibe-island★ 4100% same

    Edited · 0

    None found.

    Wrote their own version · 3

    1. steipete/agent-scripts★ 7.4ksame name
    2. kpatdev/my-skills★ 0same name
    3. kpatdev/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read CodexBar. Never mutate config/auth.

    line 8
  2. Distinctive:

    All stdout: JSON. Upstream CodexBar shape kept.

    line 21
  3. Very specific:

    Start doctor when install/config unknown.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CodexBar

Read CodexBar. Never mutate config/auth.

Run

skill="${CODEX_HOME:-$HOME/.codex}/skills/codexbar"
"$skill/scripts/codexbar" doctor
"$skill/scripts/codexbar" providers
"$skill/scripts/codexbar" usage
"$skill/scripts/codexbar" usage --provider codex
"$skill/scripts/codexbar" usage --all

All stdout: JSON. Upstream CodexBar shape kept. Less drift, fewer tokens.

Rules

  • Start doctor when install/config unknown.
  • usage reads enabled providers. Prefer this.
  • usage --provider ID reads one provider.
  • usage --all expensive; use only when needed.
  • Identities hidden by default. --include-identities only when user explicitly needs them.
  • Secrets always hidden.
  • Helper read-only: fixed allowlist only. No config writes, auth repair, enable/disable, key storage.
  • Timeout means upstream stuck. Narrow provider or raise CODEXBAR_TIMEOUT (default 120 seconds).

Binary

Auto-find: CODEXBAR_BIN, PATH, app bundle, Homebrew cask. If missing: open CodexBar, Preferences > Advanced > Install CLI; or set CODEXBAR_BIN.

Each stdout/stderr stream capped at 1 MiB while fully drained. Timeout kills process group.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.