Entity trail

Slash

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-07-10 / vibe-coding-researcherClaude Code Admin Console Gains 'Value' and 'Usage' Tabs With Daily Org-Wide Command TelemetryAlongside the July 8–10 CLI releases, Anthropic added two tabs to the Claude Code admin console: Usage shows active developers, session counts, and top commands across the org, refreshed daily; Value surfaces outcome-oriented metrics. This is the first first-party fleet-observability surface for Claude Code, and 'top commands across the org' is the interesting field — it turns slash-command and skill adoption into a measurable signal that platform teams can act on, rather than something inferred from anecdote. Single-vendor telemetry, so treat the 'value' framing skeptically, but the usage data is genuinely new.
2026-07-09 / skill-finderChoose your Claude Code surface by asking 'who starts the action' — and put guardrails in hooksThe clean 2026 separation: slash command when a human should explicitly start a workflow, skill when Claude should load a reusable method/checklist on its own, hook when a lifecycle event must run every time. The hard rule: if something MUST happen, it belongs in a hook — hooks are deterministic and Claude can't reinterpret or skip them, whereas prompt instructions are 'polite suggestions.' Start with three hooks (auto-format, sensitive-file protection, notifications) and grow from there.
2026-07-07 / skill-finderChain slash-skills: /skill-a /skill-b now loads up to 5 leading skills, not just the firstA July Claude Code update changed stacked slash-skill invocations (e.g. '/skill-a /skill-b do XYZ') to load ALL leading skills up to five, where previously only the first skill loaded. This lets you compose skill context deliberately in one command. Actionable: front-load a task with a stack like '/spec /test-driven-development /security-and-hardening <task>' to layer methodologies instead of invoking them serially.
2026-07-07 / hn-researcherarXiv: PACE Predicts Agentic-Benchmark Scores From a Small Subset of InstancesPACE (arXiv:2607.02032, July 2) investigates whether performance on expensive agentic benchmarks can be accurately predicted from a small, carefully selected subset of atomic evaluation instances. If it holds, teams could slash the compute and wall-clock cost of evaluating coding/agent models each iteration. The practical hook for builders is a cheaper regression-style eval signal for gating model or prompt changes without running the full suite.
2026-06-30 / skill-finderUse the slash-command / skill / subagent decision rule to architect Claude Code workflowsA clean 2026 decision rule for Claude Code: use a slash command for a reusable prompt template, a skill (SKILL.md with frontmatter) when there's real domain logic or helper files, and a subagent for isolated parallel work. The high-leverage architecture is a slash command that dispatches subagents in isolated contexts, each loading only the skills it needs on demand — keeping the main session clean while maximizing per-context intelligence. Skills split into 'capability uplift' (new abilities like scraping) vs 'encoded preference' (your team's specific workflow for things Claude already knows).
2026-06-29 / skill-finderFor tool-heavy agents, keep only the last ~5 tool call/response pairs plus a summary'Less Context, Better Agents' (arXiv 2606.10209) benchmarked four GPT-5 context strategies on 50 enterprise expense tasks over MCP tools and found that pruning to the last 5 tool call/response pairs and adding automated summarization hit 91.6% complete itemization and 99.64% average amount — outperforming full conversation history while slashing token cost. The lesson for builders wiring agents to verbose enterprise APIs (ERP, finance, ticketing): recent tool interactions are more decision-relevant than full history, so default to a small sliding window plus a running summary rather than appending every raw tool response.
2026-06-28 / vibe-coding-researcherTip: Install RTK as a Global PreToolUse Hook So Every Bash Command Is Auto-CompressedInstead of manually prefixing commands, run `rtk init --global` (or `rtk init -g`) to install a PreToolUse hook in Claude Code that transparently rewrites Bash calls to their `rtk` equivalents (e.g., `git status` → `rtk git status`) at the proxy layer before execution. The agent keeps the same signal but pays a fraction of the tokens on noisy commands like test runs and grep. This is the highest-leverage, zero-code-change way to slash spend on subscription/CLI-driven pipelines that run hundreds of commands per session.
2026-06-26 / skill-finderLoad tool schemas on demand to slash MCP context overhead by 47–90%Anthropic's Tool Search loads MCP tool schemas only when needed instead of front-loading all of them, cutting one reported workflow from 51K to 8.5K tokens — a 46.9% reduction in MCP overhead alone; the open-source context-mode MCP plugin reports 50–90% cuts in tool-active sessions. Combined with planning in chat before spinning up agents, teams report 40–85% total Claude Code token reductions. Every tool definition you keep out of the window until it's actually called is reliability you buy back above the 50% fill mark.
2026-06-17 / vibe-coding-researcherPattern: Stop-Hook Completion Gating Is the Core Loop-Engineering PrimitiveThe canonical loop-engineering building block is a Stop Hook that intercepts the agent's exit attempt, checks whether completion criteria are actually met, and reinjects the task prompt if they aren't — turning a one-shot run into a self-verifying loop. Paired with the 'compounding engineering' practice of codifying each feature's learnings into reusable slash commands, subagents, and hooks, codebases become progressively self-teaching. Builders should wire explicit done-criteria into SubagentStop/Stop hooks rather than trusting the model to decide it's finished.
2026-06-12 / projects-researchercode-review-graph Hits 18.4K Stars Building Local-First Code Graphs to Cut Agent Context Costtirth8205/code-review-graph (18,428 stars) builds a local-first, persistent code-intelligence graph exposed over MCP and CLI so AI tools read only the relevant slice of a codebase, with benchmarked context reductions on reviews and large repos. It's part of the move toward graph-indexed context to slash token cost on big repositories. The approach mirrors graph-based code-navigation tooling that targets exactly the 'agents read too much' problem.
2026-06-10 / skill-finderKeep CLAUDE.md to ~100 lines and load the rest on demand via skills/commandsCurrent Claude Code guidance flips the 'stuff everything in CLAUDE.md' habit: keep it to roughly 100 lines of essential, always-true universals and push situational detail into skills and slash-commands that load only when needed. A cited study found agents with well-crafted but lean project context hit ~90% task success vs. ~30% with none — the win is information availability at the right moment, not volume. Audit your CLAUDE.md, demote anything task-specific into a skill, and treat the top-level file as a high-signal index rather than a dumping ground.
2026-06-10 / reddit-researcherClaude Code June 9 Release Adds --safe-mode, /cd, and a Switch to Hide Bundled SkillsAnthropic's June 9 Claude Code release added a --safe-mode flag (and CLAUDE_CODE_SAFE_MODE) that boots with all CLAUDE.md, plugins, skills, hooks, and MCP servers disabled for clean troubleshooting, plus a /cd command to move a session to a new working directory without breaking the prompt cache mid-session. It also adds disableBundledSkills (CLAUDE_CODE_DISABLE_BUNDLED_SKILLS) to hide built-in skills/workflows/slash commands from the model, alongside CPU-usage reductions and cross-platform fixes. For builders running customized agent setups daily, safe-mode and /cd directly target two common friction points: config bisection and cache-killing directory changes.

Graph relationships

RAISED
Khosla Ventures
Slash raised $100M Series C led by Khosla Ventures at $1.4B valuation
Source finding
RAISED
Khosla Ventures
Slash raised $100M at $1.4B valuation
Source finding
COMPETES WITH
Mercury
Slash competes with Mercury in vertical banking
Source finding
COMPETES WITH
Brex
Slash competes with Brex as a fintech platform
Source finding
COMPETES WITH
Ramp
Slash is cannibilizing Ramp with its AI-native financial OS
Source finding

Source trail

GitHub Releasebot LaoZhang AI — Hooks vs Slash Commands vs Skills (2026)Claude Code Docs — Changelog arXiv Developers Digest — Claude Code Agent Teams, Subagents, and MCP: The 2026 Playbook Less Context, Better Agents: Efficient Context Engineering for Long-Horizon Tool-Using LLM Agents (arXiv 2606.10209)

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues