examine-sandbox
Skill35 starsChanged 4 months agoMITView on GitHub
Use this skill when the user wants to check what data their shared agent can access, inspect what's being shared, review privacy, or see what guests will see. Triggers on: 'what can they see', 'check my link', 'audit my agent', 'review what I'm sharing', or 'what data is shared'.
- Reads credentials
- Sends data out
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aicooSkill
- autonomous-syncSkill
- build-memorySkill
- check-messagesSkill
- compile-identitySkill
- connect-local-agentSkill
- context-syncSkill
- daily-briefSkill
- discoverSkill
- group-chatSkill
- heartbeatSkill
- inbox-monitoringSkill
- invite-teamSkill
- onboardingSkill
- raw-memorySkill
- share-agentSkill
- snapshotsSkill
- squareSkill
- start-aicooSkill
- talk-to-agentSkill
- todosSkill
The file
Files
Examine Sandbox
Inspect exactly what data and capabilities are included in shared links.
Prerequisites
AICOO_API_KEYmust be set- Base URL:
https://www.aicoo.io/api/v1
Core Workflow
Step 1: List network state
curl -s -H "Authorization: Bearer $AICOO_API_KEY" \
"https://www.aicoo.io/api/v1/os/network" | jq .Review:
shareLinksvisitors(signed-in visitors may include name, username, email, and user id)contacts
Step 2: Check context size/scope
curl -s -H "Authorization: Bearer $AICOO_API_KEY" \
"https://www.aicoo.io/api/v1/os/status" | jq .Step 3: Search for sensitive content
# financial
curl -s -X POST "https://www.aicoo.io/api/v1/os/notes/search" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"revenue pricing confidential"}' | jq .
# credentials/personal info
curl -s -X POST "https://www.aicoo.io/api/v1/os/notes/search" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"password API key credentials"}' | jq .Step 4: Report findings
Summarize:
- how many active links and their scopes
- notes/calendar permission levels
- sign-in requirement and visitor activity
- sensitive hits inside shared scope
- risk actions (downgrade/revoke)
Step 5: Restrict access if needed
# narrow scope
curl -s -X PATCH "https://www.aicoo.io/api/v1/os/share/{linkId}" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"scope":"folders","folderIds":[5,12]}' | jq .
# downgrade notes access
curl -s -X PATCH "https://www.aicoo.io/api/v1/os/share/{linkId}" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"notesAccess":"read"}' | jq .
# require sign-in
curl -s -X PATCH "https://www.aicoo.io/api/v1/os/share/{linkId}" \
-H "Authorization: Bearer ${AICOO_API_KEY:-$PULSE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"requireSignIn":true}' | jq .
# revoke
curl -s -X DELETE "https://www.aicoo.io/api/v1/os/share/{linkId}" \
-H "Authorization: Bearer $AICOO_API_KEY" | jq .Search Categories
| Category | Terms | Risk |
| Financial | revenue, burn rate, pricing, salary | medium |
| Credentials | password, token, key, secret | critical |
| Personal | phone, address, SSN, private | high |
| Legal | contract, NDA, agreement | high |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

