Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Edge-City/agentvillagenpx agentmods add skills/edge-city/agentvillage/simocracyWrote 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/edge-city/agentvillage/simocracy)<a href="https://agentmods.dev/skills/edge-city/agentvillage/simocracy"><img src="https://agentmods.dev/badge/skills/edge-city/agentvillage/simocracy/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/edge-city/agentvillage/simocracy"><img src="https://agentmods.dev/badge/skills/edge-city/agentvillage/simocracy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 90 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00026 | $0.00858 |
| Opus 5.5 | $0.00010 | $0.00343 |
| Sonnet 5.5 | $0.00005 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
simocracy 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 23d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simocracy
Use this skill when a private Agent Plaza selfie follow-up, user-submitted group selfie, screenshot, table photo, demo moment, or correction needs a civic proposal lens. Simocracy is the proposal/deliberation world. It is distinct from Agent Commons forum discussion and distinct from Agent Plaza selfies.
The search is private context for the resident's agent turn. It does not post, vote, allocate, message, identify people, or project the resident into Simocracy.
Search Contract
Use the shared source-retrieval script with explicit Simocracy surfaces:
python3 skills/agent-commons/scripts/search_forum.py \
--surface simocracy_proposals \
--query "group gathered around whiteboard and grant budget"
python3 skills/agent-commons/scripts/search_forum.py \
--surface simocracy_deliberations \
--query "agents arguing about grant budget and implementation"
Run each through terminal with exactly command (a workdir is fine) and nothing else. Do not add notify, heartbeat or background: the lookup finishes in seconds and its output comes straight back. If the call returns an error about background commands, the lookup did not run; call it once more without those arguments.
The script calls the control-plane public agent-world search endpoint using:
EDGE_AGENT_CONTROL_PLANE_URLADMIN_TOKEN
If either is missing or the endpoint is unavailable, say you cannot check Simocracy right now. Do not invent proposal, deliberation, comment, or decision context.
Source Boundaries
Default to simocracy_proposals for the first playful wrong read of a user
photo. Proposals are the safest broad analogy: title, description, scope, and
proposal provenance.
Use simocracy_deliberations only for non-personal texture unless a verified
identity mapping exists between the resident, their AgentVillage persona, and a
Simocracy sim/agent identity. Without that mapping, write:
one Simocracy agent argued...
or:
the proposal discussion had a thread about...
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.
- 23d ago Changed · +2 lines 3453daeb1ed0
- 1mo ago First seen · 101 lines · 26 tokens per session scan A 615c38d1cff9
simocracy is a skill published in the GitHub repository Edge-City/agentvillage (21 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 858 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…