Borrowing it
Nothing to install: this file belongs to rickycambrian/geo_mcp_server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rickycambrian/geo_mcp_server/main/.claude/skills/clear-dao-space/SKILL.mdgit clone --depth 1 https://github.com/rickycambrian/geo_mcp_serverWrote 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/rickycambrian/geo_mcp_server/clear-dao-space)<a href="https://agentmods.dev/skills/rickycambrian/geo_mcp_server/clear-dao-space"><img src="https://agentmods.dev/badge/skills/rickycambrian/geo_mcp_server/clear-dao-space/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rickycambrian/geo_mcp_server/clear-dao-space"><img src="https://agentmods.dev/badge/skills/rickycambrian/geo_mcp_server/clear-dao-space.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.01796 |
| Opus 5 | $0.00019 | $0.00898 |
| Sonnet 5 | $0.00008 | $0.00359 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
clear-dao-space 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clear DAO Space
Wipe ALL entities and relations from the DAO space (6b05a4fc85e69e56c15e2c6891e1df32).
IMPORTANT: This is a destructive operation. Always run with --dry-run first.
Quick Start
Dry run (fast count query, no pagination):
npm run clear-dao -- --dry-run
Fire-and-forget full deletion (loops until empty):
npx tsx scripts/clear-dao-space.ts --all --yes --batch-size 5000
Usage Examples
Dry run with limit (paginates up to N items per type for sampling):
npm run clear-dao -- --dry-run --limit 100
Test a small batch live:
npm run clear-dao -- --total-limit 100 --batch-size 100 --yes
Medium batch (5K items):
npm run clear-dao -- --total-limit 5000 --batch-size 5000 --yes
Full run with --all (loops in 50K chunks until empty):
npx tsx scripts/clear-dao-space.ts --all --yes --batch-size 5000
With space rename after clearing:
npm run clear-dao -- --all --yes --rename "New Space Name"
Flags
| Flag | Description |
|---|---|
--dry-run |
Preview what would be deleted without on-chain actions |
--limit N |
Limit N items per type (entities and relations separately) |
--total-limit N |
Limit combined total (relations processed first, then entities) |
--all |
Loop in 50K chunks until space is empty |
--yes / -y |
Skip interactive confirmation prompt |
--batch-size N |
Ops per DAO proposal (default: 5000). Each batch = one proposal + vote + execute |
--rename "Name" |
Rename the space entity after clearing |
--type <typeId> |
Only delete entities matching this type ID (targeted deletion) |
--exclude-type <typeId> |
Skip entities of this type |
How It Works
- Queries all entities in the DAO space via GraphQL (
testnet-api.geobrowser.io/graphql)- Uses
CREATED_AT_ASCordering to process oldest content first - Filters out Account-type entities and wallet-address-named entities (these are created by governance and would just be recreated)
- Uses
- Queries all relations in the space
- Builds delete ops: relations first, then entities
- For each batch:
- First batch includes Account.make() ops if no existing Account entity is found
- Subsequent batches reuse the existing Account entity ID (no new creation)
- Proposes a DAO edit via
daoSpace.proposeEdit()with FAST voting - Self-votes YES via
SpaceRegistryAbi.enter()pattern - Auto-executes if vote threshold reached; checks
DaoSpaceAbi.getLatestProposalInformation()andisSupportThresholdReached()
- Sleeps 4s between batches to avoid rate limiting
- Post-verifies by querying final entity/relation counts
- Logs progress to
backups/deletion-progress.jsonl
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.
- 10d ago First seen · 172 lines · 39 tokens per session scan A 8dad2c10cda6
clear-dao-space is a skill published in the GitHub repository rickycambrian/geo_mcp_server (0 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 1,796 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-31.
Other skills, from other repositories
adding-personhog-rpc
Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC…
bitcoin-core-indexes
Bitcoin Core indexes: txindex, blockfilterindex (BIP157/158), coinstatsindex. Disk costs, rebuild times, when each is needed. USE WHEN: choosing which indexes to enable, troubleshooting "txid not found", integrating with electrs / fulcrum / LN nodes.
slv-jetstreamer
Build, configure, and run anza-xyz/jetstreamer + ClickHouse on a dedicated analytics node. Streams Old Faithful CAR archives at multi-million-TPS into ClickHouse so historical Solana data is queryable via SQL (programinvocations, slotstatus, pubkeymentions). Includes hourly backfill timer and a rolling-window…
convex
Use when building with Convex, writing Convex functions, queries, mutations, actions, HTTP endpoints, defining database schemas/validators, configuring cron jobs, file storage, realtime subscriptions, AI agents, or security audits.
rushdb-domain-template
Design a tailored RushDB schema for any use case through guided conversation. Use this skill when a user is starting a new project, unsure what labels to define, asking "what records should I create", or wants a scaffold for a known domain (e-commerce, healthcare, SaaS, CRM, agent memory, etc.). Interviews the user…
rushdb-data-modeling
Model data in RushDB's property-centric LMPG graph. Use when designing or evolving schemas, choosing labels and properties, defining relationships, importing nested JSON, structuring a new use case, or modeling agent memory with EPISODE, MEMORYFACT, domain records, scope fields, semantic properties, and fact…