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/mcpware/cross-code-organizer/organizenpx skills add mcpware/cross-code-organizer --skill organizegit clone --depth 1 https://github.com/mcpware/cross-code-organizerWrote 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.
[](https://agentmods.dev/skills/mcpware/cross-code-organizer/organize)<a href="https://agentmods.dev/skills/mcpware/cross-code-organizer/organize"><img src="https://agentmods.dev/badge/skills/mcpware/cross-code-organizer/organize.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00031 | $0.00238 |
| Opus 5 | $0.00015 | $0.00119 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
organize 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 3d 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.
What it actually says
Organize — Claude Code Dashboard
Launch the Cross-Code Organizer (CCO) dashboard to visually manage all your customizations.
What to do
- Run the organizer server:
npx @mcpware/cross-code-organizer@latest $ARGUMENTS
-
Tell the user the dashboard is opening in their browser at
http://localhost:3847(or the next available port). -
If the user provides
--port <number>, pass it through as the argument.
What this does
Opens a drag-and-drop web dashboard showing:
- All memories, skills, MCP servers, hooks, configs, and plugins
- Shows what loads globally vs per-project (Global and Project scopes)
- Move items between scopes via drag-and-drop
- Search, filter, and preview any item
- Delete items with undo support
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.
- 3d ago First seen · 32 lines · 31 tokens per session scan A e7b3ba89c088
organize is a skill published in the GitHub repository mcpware/cross-code-organizer (376 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 238 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.
Other skills, from other repositories
githits-onboarding
Use when the user asks to install, connect, configure, sign in to, sign up for, or start using GitHits. Covers agent detection, MCP and guidance installation, authentication, verification, and setup recovery.
githits-code
Use whenever invoking the GitHits CLI for public OSS source, documentation, or example evidence, including code search/grep, file navigation, source verification, docs lookup, or canonical cross-project examples. For GitHits CLI package, dependency, security, release, or upgrade evidence, use githits-package.
githits-package
Use whenever invoking the GitHits CLI for public package or dependency evidence, including metadata, versions, licenses, vulnerabilities, dependency graphs, changelogs, release notes, or upgrade reviews.
githits-plugin-maintenance
Internal repository-maintenance skill for GitHits cross-host plugin and Agent Skill surfaces. Use only while working in the githits-cli repository when changing skills, agent guidance, plugin or marketplace manifests, Gemini or Cursor extensions, MCP transport metadata, root release metadata, plugin generation, or…
githits-mcp
Use whenever invoking GitHits MCP tools for public OSS/package evidence: package, dependency, release, security, documentation, repository source/code search, or canonical examples. Load before any GitHits MCP tool call.
githits-release
Use when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release. Covers continuous per-package release impact, version consistency, plugin manifests, MCP instruction quality, MCP registry publishing/versioning, and the special lifecycle for published Agent Skills.