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 skills add charlieviettq/awesome-agent-skill --skill grad-ambidexteritygit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/grad-ambidexterity)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/grad-ambidexterity"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-ambidexterity/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/charlieviettq/awesome-agent-skill/grad-ambidexterity"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-ambidexterity.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.00068 | $0.01242 |
| Opus 5 | $0.00034 | $0.00621 |
| Sonnet 5 | $0.00014 | $0.00248 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
"grad-ambidexterity" 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 9d 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.
This is a copy
92% identical to grad-ambidexterity — 8 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizational Ambidexterity: Exploration vs Exploitation
Overview
Organizational ambidexterity refers to a firm's ability to simultaneously pursue exploration (innovation, experimentation, new opportunities) and exploitation (efficiency, refinement, execution of existing capabilities). March (1991) demonstrated that firms favoring one over the other face suboptimal outcomes: over-exploitation leads to competency traps, while over-exploration leads to failure traps.
When to Use
Trigger conditions:
- User asks how to innovate without sacrificing current business performance
- User is restructuring an organization to support both R&D and operations
- User describes symptoms of a competency trap (good at the wrong things) or failure trap (too many experiments, no results)
- User mentions "explore vs exploit", "innovation vs efficiency", or "ambidextrous organization"
When NOT to use:
- For analyzing disruption from external entrants -> use grad-disruptive-innovation
- For strategic alliances to access innovation -> use grad-coopetition
- For internationalization decisions -> use grad-oli or grad-uppsala
Assumptions
IRON LAW: Over-Exploiting Kills Long-Term Innovation;
Over-Exploring Kills Short-Term Revenue
Exploitation WITHOUT exploration leads to a COMPETENCY TRAP: the firm
becomes excellent at yesterday's business and is blindsided by change.
Exploration WITHOUT exploitation leads to a FAILURE TRAP: the firm
burns resources on experiments that never reach market scale.
There is no stable equilibrium — the balance must be actively managed.
- Exploration and exploitation compete for scarce resources (attention, talent, budget)
- The optimal balance shifts with industry dynamism and firm lifecycle stage
- Senior leadership must actively manage the tension — it does not self-organize
Methodology
Step 1: Diagnose the Current Balance
Assess the organization's exploration-exploitation ratio:
| Indicator | Exploitation-Heavy | Balanced | Exploration-Heavy |
|---|---|---|---|
| R&D spend (% revenue) | < 3% | 5-15% | > 20% |
| New product revenue (% total) | < 10% | 20-40% | > 50% |
| Time horizon of projects | < 1 year | Mixed | > 3 years |
| Tolerance for failure | Very low | Moderate | Very high |
| Process formalization | Rigid | Adaptive | Chaotic |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 118 lines · 68 tokens per session scan A 78c9262d9fef
"grad-ambidexterity" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,242 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to grad-ambidexterity, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
punch-list-manager
Digital punch list management for construction project closeout. Track deficiencies, assign corrections, photo documentation, and completion verification.
safety-inspection
Digital safety inspection system for construction sites. Checklists, hazard tracking, incident reporting, and compliance documentation.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.
data-silo-detection
Detect and map data silos in construction organizations. Identify disconnected data sources and integration opportunities.