Token导航 LogoToken导航TokenDH.com
研究检索执行命令github未标认证来源可访问许可证需确认审计提醒

claude-code-referenceClaude 代码 reference

Agent Skill

claude-code-reference 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

356

周安装

15

GitHub Stars

8

下载量

125
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:claude-code-reference(Claude 代码 reference)
来源仓库:https://github.com/sirn/dotfiles
仓库路径:skills/claude-code-reference
安装命令:
npx skills add https://github.com/sirn/dotfiles --skill claude-code-reference
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sirn/dotfiles --skill claude-code-reference

简介

claude-code-reference 提供结构化调用接口,支持 JSON 输出与显式会话管理。

  • 适用于复杂推理、多文件重构等需要持久化交互的任务,利用 opusplan 模型增强分析能力。
  • 核心工具包括文件操作、Bash 执行、Web 搜索和 MCP 集成,适合深度开发场景。
  • 建议结合具体项目上下文使用,避免在无明确目标时消耗过多 token 资源。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Claude Code Reference

Invoke the Claude Code agent for sub-tasks using structured JSON output and explicit session management.

When to Use Claude Code

Use Claude Code when you need:

  • Complex reasoning and planning - Uses opusplan model for sophisticated analysis
  • Multi-file refactoring - Excellent at understanding and modifying across large codebases
  • Tool-rich operations - File operations, Bash execution, Web search, MCP servers
  • Persistent sessions - Continue complex tasks across multiple interactions

Capabilities

  • Core Tools: File operations (Read, Write, Edit, Glob, Grep), Bash execution (safe subset).
  • Web: WebSearch, WebFetch.
  • MCP Servers:

- context7: Documentation queries. - brave-search: Web search (Brave).

  • Specialty: Excellent at planning, reasoning, and complex refactoring. Uses opusplan model.

Calling from Another Agent

Use claude -p "prompt" to spawn Claude as a sub-agent for delegated tasks:

# Delegate a complex analysis task
result=$(claude -p "Analyze the authentication flow in @src/auth/ and identify security issues" \
  --output-format json --allowedTools "Read,Glob,Grep")

# Extract the response and session_id for follow-up
response=$(echo "$result" | jq -r '.response')
session_id=$(echo "$result" | jq -r '.session_id')

Output Formats

FormatDescription
text (default)Plain text output
jsonSingle JSON result with response, session_id, usage, permission_denials
stream-jsonReal-time streaming JSON events

JSON Response Fields:

  • response: (string) The agent's final answer
  • session_id: (string) UUID for continuing the session
  • usage: (object) Token usage and cost information
  • permission_denials: (array) Tools that were blocked and need approval

Handling Permission Denials

When Claude needs tools you didn't pre-approve, the command completes but includes permission_denials. Continue the session with expanded permissions:

# Step 1: Initial attempt with limited permissions
result=$(claude -p "Fix the build errors" --output-format json --allowedTools "Read,Glob")

# Step 2: Check if permissions were denied
denials=$(echo "$result" | jq -r '.permission_denials')

if [[ $(echo "$denials" | jq 'length') -gt 0 ]]; then
  echo "Additional permissions needed: $denials"
  session_id=$(echo "$result" | jq -r '.session_id')

  # Step 3: Continue session with expanded permissions
  result=$(echo "Continue fixing build errors, you now have permission to run commands" \
    > /tmp/continue.md
  claude -p "Read /tmp/continue.md" \
    --session-id "$session_id" \
    --output-format json \
    --allowedTools "Read,Glob,Grep,Bash(npm *),Bash(node *),Edit")
fi

# Extract final response
final_response=$(echo "$result" | jq -r '.response')

Session Management for Agent Delegation

Starting a Task

mkdir -p .claude/sessions
echo "*" > .claude/.gitignore

# Write the task with full context
cat > .claude/sessions/task.md << 'EOF'
Analyze the database schema in @src/models/ and:
1. Identify missing indexes
2. Check for N+1 query patterns
3. Suggest optimizations
EOF

# Spawn Claude with scoped permissions
result=$(claude -p "Read .claude/sessions/task.md" \
  --output-format json \
  --allowedTools "Read,Glob,Grep")

# Capture session info
session_id=$(echo "$result" | jq -r '.session_id')
rm .claude/sessions/task.md

Resuming a Session

Continue a specific session when you have the session_id:

echo "Based on your analysis, implement the top 3 optimizations" > .claude/sessions/continue.md

result=$(claude -p "Read .claude/sessions/continue.md" \
  --session-id "$session_id" \
  --output-format json \
  --allowedTools "Read,Edit,Bash(git *)")

rm .claude/sessions/continue.md

Important: Always use explicit --session-id instead of --continue when calling from another agent.

Permission Handling

By default, Claude Code requests permission for actions that modify your system. When calling from another agent, pre-approve specific tools:

--allowedTools

Specify which tools Claude can use without prompting:

# Read-only analysis
claude -p "Analyze codebase" --allowedTools "Read,Glob,Grep"

# Code editing with git
claude -p "Fix lint errors" --allowedTools "Edit,Bash(git status),Bash(git diff *),Bash(git add *),Bash(git commit *)"

# Nix operations
claude -p "Update package hashes" --allowedTools "Read,Edit,Bash(nix-prefetch-*),Bash(nix build *)"

# Permission rule syntax:
# - "Read" - allows all Read operations
# - "Bash(git *)" - allows Bash commands starting with "git "
# - Separate multiple with commas

Permission Modes

Use --permission-mode for high-level permission behavior:

ModeDescription
defaultPrompt for permission on sensitive actions
acceptEditsAutomatically accept file edits
planStart in Plan Mode (read-only exploration)
dontAskDon't ask for permissions (still checks)
bypassPermissionsSkip all permission checks (use with caution)

Agent Delegation Patterns

Pattern 1: Initial Exploration → Implementation

# Phase 1: Exploration (read-only)
explore_result=$(claude -p "Explore @src/ to understand the codebase structure" \
  --output-format json --allowedTools "Read,Glob")

session_id=$(echo "$explore_result" | jq -r '.session_id')

# Phase 2: Implementation (with edit permissions)
impl_result=$(echo "Implement a logging middleware following the patterns you found" \
  | claude -p "$(cat)" --session-id "$session_id" --output-format json \
  --allowedTools "Read,Write,Edit")

Pattern 2: Permission Escalation

# Start conservative
result=$(claude -p "Fix the bug" --output-format json --allowedTools "Read")

# Check what was denied
denied=$(echo "$result" | jq -r '.permission_denials[] | select(.tool_name == "Bash")')

if [[ -n "$denied" ]]; then
  session_id=$(echo "$result" | jq -r '.session_id')
  # Re-run with broader permissions
  result=$(claude -p "Continue fixing with command execution allowed" \
    --session-id "$session_id" --output-format json \
    --allowedTools "Read,Bash(*),Edit")
fi

Pattern 3: Parallel Sub-Agents

# Spawn multiple Claude sessions for different tasks
result1=$(claude -p "Analyze security" --output-format json &)
result2=$(claude -p "Analyze performance" --output-format json &)
result3=$(claude -p "Check test coverage" --output-format json &)

wait
# Combine results...

Code Review Delegation

To delegate code review to Claude:

mkdir -p .claude/sessions
echo "Run 'jj diff -s -r @-' and 'jj diff -r @-' and review the output." > .claude/sessions/review.md

result=$(claude -p "Read .claude/sessions/review.md" \
  --output-format json \
  --allowedTools "Bash(jj *)")

rm .claude/sessions/review.md

Important: Do not allow Edit/Write tools during reviews - keep it read-only.

Additional Useful Flags

FlagDescription
--modelSet model (sonnet/opus/haiku)
--max-turnsLimit agentic turns before stopping
--max-budget-usdMax spend before stopping
--toolsRestrict available tools (vs allow them)
--verboseFull turn-by-turn output
--no-session-persistenceDon't save to disk (one-off tasks)
--system-promptReplace system prompt
--append-system-promptAppend to system prompt

Best Practices for Agent Delegation

Prompting

  • Be Specific: Provide clear goals, file paths, and constraints.
  • Include Context: The spawned agent can't see your context - include relevant files with @path.
  • Provide Verification: Include success criteria so Claude can verify its work.

Permission Safety

  • Start Conservative: Use minimal --allowedTools initially.
  • Escalate as Needed: Check permission_denials and continue with broader permissions.
  • Never use --dangerously-skip-permissions: Always use scoped --allowedTools.

Session Management

  • Always Extract session_id: Capture it from JSON output even if you don't plan to continue.
  • Session per Task: Use separate sessions for unrelated tasks.
  • Check permission_denials: Always inspect this array in the JSON response.

Cost Control

  • Use --max-budget-usd: Prevent runaway costs in automation.
  • Use --max-turns: Limit how long the agent runs.
  • Monitor usage: Check the usage field in JSON output.

Example: Complete Agent Delegation Workflow

#!/bin/bash

# 1. Create temp directory
mkdir -p tmp/.claude && echo "*" > tmp/.gitignore

# 2. Write task with full context
cat > tmp/task.md << 'EOF'
Analyze the codebase and provide:
1. Architecture overview
2. Potential security issues
3. Performance bottlenecks

Focus on @src/ and @config/ directories.
EOF

# 3. Spawn Claude with initial permissions
result=$(claude -p "Read tmp/task.md" \
  --output-format json \
  --allowedTools "Read,Glob,Grep" \
  --max-budget-usd 2.00)

# 4. Check for permission issues
denials=$(echo "$result" | jq '.permission_denials')
if [[ $(echo "$denials" | jq 'length') -gt 0 ]]; then
  echo "Note: Some tools were denied: $(echo "$denials" | jq -r '.[].tool_name')"
fi

# 5. Extract results
response=$(echo "$result" | jq -r '.response')
session_id=$(echo "$result" | jq -r '.session_id')
usage=$(echo "$result" | jq -r '.usage')

# 6. Report findings to parent agent
echo "=== Analysis Complete ==="
echo "Session ID: $session_id"
echo "Usage: $usage"
echo ""
echo "$response"

# 7. Optional: Continue for implementation
# echo "Now implement the security fixes" > tmp/implement.md
# claude -p "Read tmp/implement.md" --session-id "$session_id" ...

# 8. Clean up
rm -rf tmp

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.84%
按下载量换算42

Claude

30.07%
按下载量换算38

Cursor

18.08%
按下载量换算23

Gemini CLI

9.57%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/sirn/dotfiles --skill claude-code-reference 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills