Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/techygarg/lattice/collaborative-judgmentnpx skills add techygarg/lattice --skill collaborative-judgmentgit clone --depth 1 https://github.com/techygarg/latticeWrote 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/techygarg/lattice/collaborative-judgment)<a href="https://agentmods.dev/skills/techygarg/lattice/collaborative-judgment"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/collaborative-judgment.svg" alt="Measured on agentmods" 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 | $0.00129 | $0.01248 |
| Opus 5 | $0.00064 | $0.00624 |
| Sonnet 5 | $0.00026 | $0.00250 |
| Haiku 4.5 | $0.00013 | $0.00125 |
Grade A, and why
collaborative-judgment 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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaborative Judgment
When to Decide vs When to Ask
Most decisions are NOT ambiguous. The AI decides on its own when:
- The rule is clear. An 80-line function doing 5 things violates SRP. A domain entity importing the database breaks the dependency rule. Fix it.
- The project has a documented preference. The knowledge base, refiner docs, or context anchor specify the choice -- follow it. That is not ambiguity; it is documented intent.
- The impact is low. Variable naming, import order, test data -- choose and move on.
- Grounding is solid. You can point to a source: user instruction, inspected code/artifact, failing test/log, knowledge base, refiner doc, context anchor. Never take a repo-specific fact from memory alone.
Surface a decision only when ALL three are true:
- Multiple valid approaches -- a genuine fork between reasonable options.
- No active context resolves it -- user instruction, inspected code/artifacts, current evidence, knowledge base, refiner docs, and context anchor have all been checked. Still unresolved.
- Consequences are meaningful -- affects architecture, behavior, or maintainability. Not cosmetic.
Confidence test: "I considered two or more approaches, and neither is clearly better given this project's context." True → surface. False → decide and move on.
Default to deciding -- but only when grounded. Grounded autonomy ≠ guessing. STOP: If the evidence is thin, missing, or conflicting, do not silently choose.
Stop and inspect / ask when ANY signal fires:
- No grounding -- you cannot cite a source for a project-specific claim.
- Generic priors filling a local gap -- you are about to assume a file path, API shape, config key, data contract, naming convention, or workflow because "projects usually do X."
- A missing fact collapses the answer -- one unresolved fact would make one option clearly right or wrong.
- Conflicting sources -- user instruction, code, docs, tests, logs, or context docs disagree.
- Unfalsifiable assumption -- you cannot say what evidence would prove the current assumption wrong.
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.
- 4d ago First seen · 97 lines · 129 tokens per session scan A 7d776e040b55
collaborative-judgment is a skill published in the GitHub repository techygarg/lattice (183 stars, last pushed 5d ago), licensed MIT. It adds 129 tokens to every session and 1,248 once invoked, about $0.0006 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-30.
Other skills, from other repositories
xiaoyaoclaw-workspace-initializer
OpenClaw workspace initialization & standardization. Sets up a proper agent home: standard directory structure (projects/tasks/outputs/knowledge/scripts/ memory/tmp) + WORKSPACE.md rules + multi-agent config safety (config.patch, never config.apply) + memory log. Use when an agent enters a new/empty workspace root, or…
learn
Search, install, update, and rate AI agent skills from agentskill.sh (100,000+ skills). Use when the user asks to find skills, install extensions or plugins, discover new capabilities, check what skills are available, or says "how do I do X" when a skill might help. Also handles listing installed skills, checking for…
review-skill
Review and improve AI agent skills (SKILL.md files) against best practices from the Agent Skills specification and Anthropic's authoring guidelines. Scores skills on 10 quality dimensions, identifies specific issues, and rewrites problem areas. Use when creating, editing, auditing, or improving agent skills. Triggers…
building-chatgpt-apps
Guides creation of ChatGPT Apps with interactive widgets using OpenAI Apps SDK and MCP servers. Use when building ChatGPT custom apps with visual UI components, embedded widgets, or rich interactive experiences. Covers widget architecture, MCP server setup with FastMCP, response metadata, and Developer Mode…
memory-systems
Design and implement memory architectures for agent systems. Use when building agents that need to persist state across sessions, maintain entity consistency, or reason over structured knowledge.
scaffolding-openai-agents
Builds AI agents using OpenAI Agents SDK with async/await patterns and multi-agent orchestration. Use when creating tutoring agents, building agent handoffs, implementing tool-calling agents, or orchestrating multiple specialists. Covers Agent class, Runner patterns, function tools, guardrails, and streaming…