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.
npx agentmods add skills/nako0/devglobe-extension/codex-pluginnpx skills add Nako0/devglobe-extension --skill codex-plugingit clone --depth 1 https://github.com/Nako0/devglobe-extensionWhat 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 | $0.00045 | $0.00627 |
| Opus 5 | $0.00023 | $0.00313 |
| Sonnet 5 | $0.00009 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade C, and why
devglobe scanned grade C with 2 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
echo "Feature flag: $(grep codex_hooks ~/.codex/config.toml 2>/dev/null || echo 'NOT SET')" Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
DEVGLOBE_SKILL="$(find ~/.codex/skills -name SKILL.md \( -path '*devglobe*' -o -path '*codex-plugin*' \) 2>/dev/null | head -1 | xargs dirname)" What it actually says
DevGlobe for Codex
Track your coding activity on devglobe.app — an interactive 3D globe showing developers coding in real-time.
Visibility settings (anonymous mode, repo sharing on the live globe, profile mode) are managed on devglobe.app/dashboard/settings.
Before running any command below, locate the installed skill directory:
DEVGLOBE_SKILL="$(find ~/.codex/skills -name SKILL.md \( -path '*devglobe*' -o -path '*codex-plugin*' \) 2>/dev/null | head -1 | xargs dirname)"
Setup
$devglobe setup <API_KEY>
Configure DevGlobe with your API key. Get your key at devglobe.app.
echo '{"api_key":"<API_KEY>"}' | node "$DEVGLOBE_SKILL/dist/setup.js"
This will:
- Save your API key to
~/.devglobe/config.toml(mode0600) - Install Codex hooks at
~/.codex/hooks.jsonfor automatic heartbeats - Enable the
codex_hooksfeature flag in~/.codex/config.toml
After setup, restart Codex for hooks to take effect.
Status
$devglobe status <MESSAGE>
Set a status message displayed on the globe next to your avatar.
echo '{"message":"<MESSAGE>"}' | node "$DEVGLOBE_SKILL/dist/update-status.js"
The script reads the API key from ~/.devglobe/config.toml directly.
Diagnostics
$devglobe check
Verify the installation is working:
echo "=== DevGlobe Status ==="
echo "Config: $(test -f ~/.devglobe/config.toml && echo OK || echo 'NOT SET')"
echo "API key set: $(awk -F'"' '/^api_key/ {print ($2 != "" ? "yes" : "no")}' ~/.devglobe/config.toml 2>/dev/null || echo 'NOT SET')"
echo "Hooks: $(grep -cE 'devglobe|codex-plugin' ~/.codex/hooks.json 2>/dev/null || echo 0) references in hooks.json"
echo "Feature flag: $(grep codex_hooks ~/.codex/config.toml 2>/dev/null || echo 'NOT SET')"
$devglobe uninstall
Remove DevGlobe hooks from Codex:
echo '{}' | node "$DEVGLOBE_SKILL/dist/uninstall.js"
What ships with it
22 files 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.
- .gitignore 21 B
- agents/openai.yaml 116 B
- dist/index.js 23 KB runs code
- dist/setup.js 9.5 KB runs code
- dist/uninstall.js 1.4 KB runs code
- dist/update-status.js 8.9 KB runs code
- package-lock.json 15 KB
- package.json 602 B
- README.md 4.2 KB
- references/hooks-template.json 757 B
- scripts/find-node 483 B
- scripts/heartbeat 275 B
- scripts/setup 392 B
- scripts/uninstall 404 B
- scripts/update-status 416 B
- src/hooks.ts 227 B runs code
- src/index.ts 3.8 KB runs code
- src/setup.ts 2.8 KB runs code
- src/types.ts 364 B runs code
- src/uninstall.ts 1.4 KB runs code
- src/update-status.ts 1015 B runs code
- tsconfig.json 351 B
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.
- yesterday First seen · 65 lines · 45 tokens per session scan C da261e1f79b3
devglobe is a skill published in the GitHub repository Nako0/devglobe-extension (213 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 627 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
team-lead-collaboration
Markdown collaboration Lead. Use only when the user explicitly selects $team-lead-collaboration to organize lightweight project collaboration.
team-member-collaboration
Markdown collaboration Member. Use only when the user explicitly selects $team-member-collaboration for assigned project work.
github
Integração com GitHub — issues, PRs, repositórios, código e actions via MCP.
bridge
Use when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.ai web, or IDE extensions that don't load CLI plugins. Writes a managed doctrine block into the project's CLAUDE.md so autonomy + intent-routing + commit cadence + role separation + file-first rules…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
livecodes/sdk-methods
Use SDK methods to interact with playgrounds: run, getCode, setConfig, getConfig, watch, runTests, format, getShareUrl, show, destroy. Load this skill when programmatically controlling embedded playgrounds, reacting to code changes, or retrieving compiled output.