agentica-claude-proxy — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited agentica-claude-proxy (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when developing or debugging the Agentica-Claude proxy integration.
Agentica Agent → S_M_BASE_URL → Claude Proxy → claude -p → Claude CLI (with tools)
(localhost:2345) (localhost:8080)Claude CLI in -p mode restricts file operations. You MUST add:
subprocess.run([
"claude", "-p", prompt,
"--append-system-prompt", system_prompt,
"--allowedTools", "Read", "Write", "Edit", "Bash", # REQUIRED
])Without this, agents will report "permission denied" for Write/Edit operations.
Agentica expects SSE streaming, not plain JSON:
# Response format
yield f"data: {json.dumps(chunk)}\n\n"
yield "data: [DONE]\n\n"Agents MUST return results as Python code blocks with a return statement:
return "your result here"Agentica's REPL parser extracts code between \\\python and \\\.
Agents will hallucinate success without actually using tools unless you explicitly warn them:
## ANTI-HALLUCINATION WARNING
**STOP AND READ THIS CAREFULLY:**
You have access to these tools: Read, Write, Edit, Bash
When the task asks you to create/modify/run something:
1. FIRST: Actually invoke the tool (Read, Write, Edit, or Bash)
2. SECOND: Wait for the tool result
3. THIRD: Then return your answer based on what actually happened
**DO NOT** skip the tool invocation and just claim success!
If you didn't invoke a tool, you CANNOT claim the action succeeded.Both Claude Code and Agentica have sandboxes:
/tmp/ paths are blocked by Claude CodeSolution: Use project-relative paths like workspace/ instead of /tmp/
cat logs/agent-<N>.logNote: Logs only show final conversational response, not tool invocations.
curl -s http://localhost:8080/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{"model": "claude", "messages": [{"role": "user", "content": "Create file at workspace/test.txt"}], "stream": false}'# After agent claims to create file
ls -la workspace/test.txt
cat workspace/test.txt# Terminal 1: Proxy
uv run python scripts/agentica/claude_proxy.py --port 8080
# Terminal 2: Agentica Server
cd workspace/agentica-research/agentica-server
INFERENCE_ENDPOINT_URL=http://localhost:8080/v1/chat/completions uv run agentica-server --port 2345S_M_BASE_URL=http://localhost:2345 uv run python your_script.pycurl http://localhost:8080/health # Proxy
curl http://localhost:2345/health # Agenticascripts/agentica/claude_proxy.pyscripts/agentica/claude_proxy.py:49-155workspace/test_swarm_all_tools.pyscripts/agentica/dependency_swarm.py| Error | Cause | Fix |
|---|---|---|
| "Permission denied" | Missing --allowedTools | Add --allowedTools Read Write Edit Bash |
| Agent claims success but file not created | Hallucination | Add anti-hallucination prompt section |
| "Cannot access /tmp/..." | Sandbox restriction | Use project-relative paths |
| "APIConnectionError" | Wrong response format | Use SSE streaming (data: {...}\n\n) |
| "NameError: view_file" | Agent using REPL functions | Add REPL_BASELINE with native tool examples |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.