grad-mechanism-design

grad-mechanism-design is a skill for Claude Code from martineserios/thebrana. It costs 40 tokens per session (1,129 once invoked), scanned A, a copy of grad-mechanism-design, MIT.

A guide to mechanism design, the study of rules that shape how people or automated participants make choices when they have private information.

In plain words
What is it for?
Use it to design or assess allocation rules, auctions, voting systems, matching markets, and incentive structures.
Why use it?
It helps evaluate whether auctions, voting systems, or matching processes encourage truthful participation and produce suitable outcomes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the brana plugin — 53 skills, 4 commands, 14 agents shipped together

Good fit Use it to design or assess allocation rules, auctions, voting systems, matching markets, and incentive structures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/martineserios/thebrana/grad-mechanism-design
Install

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.

Any agent
npx skills add martineserios/thebrana --skill grad-mechanism-design
Clone the repo
git clone --depth 1 https://github.com/martineserios/thebrana

Made for: Claude Code.

Or install brana, the plugin that ships this one along with the rest of its 53 skills, 4 commands, 14 agents.

Wrote 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.

agentmods badge for grad-mechanism-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/martineserios/thebrana/grad-mechanism-design/github.svg)](https://agentmods.dev/skills/martineserios/thebrana/grad-mechanism-design)
Your own site
<a href="https://agentmods.dev/skills/martineserios/thebrana/grad-mechanism-design"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/grad-mechanism-design/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.

agentmods 80×15 button for grad-mechanism-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/martineserios/thebrana/grad-mechanism-design"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/grad-mechanism-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,129 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01129
Opus 5.5 $0.00016 $0.00452
Sonnet 5.5 $0.00008 $0.00226
Haiku 4.5 $0.00004 $0.00113

Measured 1mo ago against content hash 1f4fe95fca5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

grad-mechanism-design 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 1mo 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.

Origin

This is a copy

86% identical to grad-mechanism-design — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

system/skills/grad-mechanism-design/SKILL.md · 103 lines

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.

Mechanism Design: Reverse Game Theory and Incentive Compatibility

Overview

Mechanism design is the engineering side of game theory: instead of analyzing given games, you design the rules so that self-interested agents produce a desired outcome. The central tool is the revelation principle, which shows that any implementable outcome can be achieved by a direct mechanism where truth-telling is optimal. The field underpins auction design, voting systems, matching markets, and regulatory frameworks.

When to Use

  • Designing allocation rules (auctions, matching, resource sharing) where participants have private information
  • Evaluating whether a proposed institution or platform incentivizes truthful behavior
  • Assessing trade-offs between efficiency, budget balance, and participation constraints

When NOT to Use

  • Agents are fully cooperative with no private information (no incentive problem exists)
  • The environment is too complex to model agent types (use behavioral experiments instead)
  • You need a quick heuristic rather than a formal guarantee

Assumptions

IRON LAW: A mechanism is incentive-compatible ONLY if truth-telling is a
dominant strategy — no mechanism can simultaneously maximize efficiency,
budget balance, and individual rationality (Myerson-Satterthwaite theorem).
  • Agents are rational and maximize expected utility
  • Each agent has private information (type) drawn from a known prior distribution
  • The designer commits to the mechanism rules before agents act
  • Transfers (payments) are feasible and quasi-linear utility applies

Methodology

Step 1 — Define the Design Problem Specify the set of agents, their type spaces, the outcome space, and the social choice function you want to implement. Identify the objective: efficiency, revenue, fairness, or a weighted combination.

Step 2 — Apply the Revelation Principle Restrict attention to direct revelation mechanisms. For each agent, the mechanism asks for a reported type and maps the profile of reports to an outcome and transfers. Check whether truthful reporting constitutes a Bayesian Nash equilibrium (BNE-IC) or dominant strategy equilibrium (DSIC).

Read the full file on GitHub · 103 lines

Changes

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.

  1. 1mo ago First seen · 103 lines · 40 tokens per session scan A 1f4fe95fca5f

Subscribe to this mod's changes

grad-mechanism-design is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,129 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to grad-mechanism-design, differing in 15 lines, and is treated as a copy.