mcpbeat Sign in

Grad Strat Agency Agent Skill

Apply Agency Theory (Jensen and Meckling, 1976) to diagnose principal-agent problems — moral hazard, adverse selection — and design governance mechanisms to align interests. Use this skill when the user needs to analyze conflicts of interest between owners and managers, design incentive or monitoring structures, evaluate corporate governance effectiveness, or when they ask 'how do we ensure managers act in shareholders interest', 'why is this incentive plan failing', or 'what governance mechanisms reduce agency costs'.

3k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-strat-agency

What comes with it

7 859 bytes besides the instruction
examples/sample_scenario.md

The instruction itself

14 sections, as written by the author

Agency Theory

Overview

Agency theory addresses the relationship where one party (principal) delegates work to another (agent) whose interests may diverge. Jensen and Meckling (1976) formalized how the separation of ownership and control creates agency costs: monitoring costs, bonding costs, and residual loss.

When to Use

  • Analyzing owner-manager conflicts in corporate governance
  • Designing executive compensation and incentive plans
  • Evaluating board effectiveness and monitoring structures
  • Assessing governance in franchising, partnerships, or supply chains

Assumptions

IRON LAW: Agency costs are unavoidable — the goal is to minimize
TOTAL agency costs (monitoring + bonding + residual loss).
Eliminating one cost type often increases another. Optimal
governance minimizes the sum, not any single component.

Key assumptions:

  • Goal divergence — Agents have self-interest that may conflict with principals
  • Information asymmetry — Agents possess private information
  • Risk preferences differ — Agents are typically more risk-averse than diversified principals

Methodology

Agency Problem Types

| Problem | When | Mechanism |

|---------|------|-----------|

| Moral hazard | Post-contract; agent effort is unobservable | Hidden action |

| Adverse selection | Pre-contract; agent type is unobservable | Hidden information |

| Hold-up | Post-investment; agent exploits lock-in | Relationship-specific investment |

Agency Cost Components

  • Monitoring costs — Expenses by principal to observe agent behavior (audits, boards, reporting)
  • Bonding costs — Expenses by agent to signal alignment (certifications, guarantees)
  • Residual loss — Remaining welfare loss despite monitoring and bonding

Governance Design Steps

  • Identify the principal-agent relationship — Who delegates? Who acts?
  • Diagnose the agency problem — Moral hazard, adverse selection, or both?
  • Assess information asymmetry — What can the principal observe?
  • Design mechanisms:
  • Outcome-based contracts — Align incentives (bonuses, stock options, profit sharing)
  • Behavior-based monitoring — Observe and constrain (board oversight, audits, reporting)
  • Bonding mechanisms — Agent credible commitments (warranties, certifications)
  • Evaluate total cost — Ensure mechanism cost does not exceed agency cost saved

Output Format

## Agency Analysis: [Context]

### Principal-Agent Map
| Principal | Agent | Delegation | Key Conflict |
|-----------|-------|-----------|--------------|
| [who]     | [who] | [what]    | [goal divergence] |

### Agency Problem Diagnosis
- Type: [moral hazard / adverse selection / both]
- Information asymmetry: ...
- Observable vs unobservable: ...

### Governance Mechanisms
| Mechanism | Type | Cost | Expected Effect |
|-----------|------|------|-----------------|
| [name]    | [monitoring/bonding/incentive] | [est.] | [reduction in...] |

### Total Agency Cost Assessment
- Monitoring costs: ...
- Bonding costs: ...
- Estimated residual loss: ...

Examples

Good Example

Analyzing CEO compensation: principal (shareholders) faces moral hazard (CEO effort unobservable). Design combines outcome-based incentives (stock options aligned with long-term value) with behavior-based monitoring (independent board, audit committee). Evaluates trade-off between monitoring intensity and incentive pay.

Bad Example

Proposing "more monitoring" without considering that excessive monitoring increases costs and may crowd out intrinsic motivation. Agency theory requires minimizing total agency costs, not maximizing control.

Gotchas

  • Multiple principals with conflicting goals (shareholders vs debtholders vs employees) complicate analysis
  • Stock options can create perverse incentives (short-term manipulation, excessive risk-taking)
  • Agency theory assumes self-interest; it may underweight stewardship motivations
  • Board independence does not automatically equal effective monitoring
  • In non-corporate contexts (franchises, alliances), identify who is principal and who is agent carefully

References

  • Jensen, M. & Meckling, W. (1976). Theory of the firm: Managerial behavior, agency costs and ownership structure. *Journal of Financial Economics*, 3(4), 305-360.
  • Eisenhardt, K. (1989). Agency theory: An assessment and review. *Academy of Management Review*, 14(1), 57-74.
  • Fama, E. & Jensen, M. (1983). Separation of ownership and control. *Journal of Law and Economics*, 26(2), 301-325.

Other skills for the same job

different authors, same section of the catalogue
MCP Deploy Manage Agents
by github
vendor ×1

Skill converted from mcp-deploy-manage-agents.prompt.md

2k tokens
Cloud Claw Launch Agent
by internet-court
×1

Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw-* commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs; use cloud-claw-manage-vm.

1k tokens
Hosted Agents V2 Py
by lingxling
×1

Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.

2k tokens
Cloudflare MCP Server
by ComeOnOliver
×1

Build MCP (Model Context Protocol) servers on Cloudflare Workers with tools, resources, and prompts.

49k tokens scripts
When Chaining Agent Pipelines Use Stream Chain
by ComeOnOliver
×1

Chain agent outputs as inputs in sequential or parallel pipelines for data flow orchestration

5k tokens
Clone Audit Mrlv3nl4
by nexu-io

Audit cloned or reimplemented websites for fidelity gaps, tracking scripts, source-brand and language residue, placeholders, and risky external dependencies. Use before handoff or deployment, or when asked to review a website clone for cleanup and readiness.

2k tokens
Hermes Tweet
by wshobson

> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated tweet actions. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing guarded tweet actions. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.

2k tokens
Arize Evaluator
by github
vendor

Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.

10k tokens

How to use it

Copy the folder

Take asgard-ai-platform/grad-strat-agency from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.