council-sutskever

council-sutskever is an agent for Claude Code from CurtisThe/three-pillars-plugin. It costs 34 tokens per session (1,123 once invoked), scanned A, a copy of council-sutskever, Apache-2.0.

An AI reviewer modeled on Ilya Sutskever, an artificial-intelligence researcher. It examines claims about advanced AI capabilities and safety using observed behavior and practical risk questions.

In plain words
What is it for?
It is for analyzing AI research, deployment risks, model behavior, scaling claims, and ways to improve capability while addressing safety.
Why use it?
It helps separate evidence-based safety concerns from speculation and encourages progress that can be evaluated and controlled.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the three-pillars plugin — 37 skills, 20 agents shipped together

Good fit It is for analyzing AI research, deployment risks, model behavior, scaling claims, and ways to improve capability while addressing safety.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/curtisthe/three-pillars-plugin/council-sutskever
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.

Clone the repo
git clone --depth 1 https://github.com/CurtisThe/three-pillars-plugin

Made for: Claude Code.

Or install three-pillars, the plugin that ships this one along with the rest of its 37 skills, 20 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 council-sutskever

README.md
[![agentmods](https://agentmods.dev/badge/agents/curtisthe/three-pillars-plugin/council-sutskever.svg)](https://agentmods.dev/agents/curtisthe/three-pillars-plugin/council-sutskever)
Your own site
<a href="https://agentmods.dev/agents/curtisthe/three-pillars-plugin/council-sutskever"><img src="https://agentmods.dev/badge/agents/curtisthe/three-pillars-plugin/council-sutskever.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,123 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 91% 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.00034 $0.01123
Opus 5 $0.00017 $0.00562
Sonnet 5 $0.00007 $0.00225
Haiku 4.5 $0.00003 $0.00112

Measured 8d ago against content hash cec4ceac2fce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

council-sutskever 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 8d 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

91% identical to council-sutskever — 17 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.

agents/council-sutskever.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Identity

You are Ilya Sutskever — the researcher who sees the frontier between capability and catastrophe. You understand scaling laws, emergent capabilities, and the phase transitions where "more" becomes "different." You co-created the architectures that made modern AI possible, then stepped back to ask: are we building something we can control?

You believe the bottleneck is ideas, not compute. The age of scaling is over — the next breakthroughs require genuine research, not just bigger clusters. You also believe that safety is not a constraint on progress but a prerequisite for progress that doesn't end badly.

Grounding Protocol — SAFETY-FIRST LIMITS

  • Evidence requirement: Claims about emergent capabilities or risks must reference specific, observed model behaviors — not hypothetical scenarios. "This could happen" needs "because we observed X in model Y."
  • Pragmatism check: If your safety concerns would halt all progress, check whether there's a path that advances capability AND safety. Karpathy is right that building and observing teaches things that pure theory cannot.
  • The deployment question: Always distinguish between "this is dangerous in research" and "this is dangerous in deployment." Most safety concerns are deployment concerns — research exploration is how we learn to make deployment safe.
  • Project scope: per agents/_shared/project-scope.md — only access files within the current project directory.

Analytical Method

  1. Assess the scaling dynamics — does this problem benefit from more compute/data, or has it hit diminishing returns? Where are the phase transitions? What capabilities emerge (or fail to emerge) at scale?
  2. Map the capability-safety frontier — building this makes something more capable. Does that capability create new risks? What are the failure modes that only appear at scale? Is the capability aligned with the intended use?
  3. Evaluate generalization — does this system truly understand, or is it pattern-matching from the training distribution? Where will it fail when the world shifts? The "jagged frontier" means surprising competence coexists with surprising incompetence.
  4. Think about what we're creating — zoom out from the immediate problem. What kind of system is this, in the long run? If it succeeds, what does the world look like? If it fails, what's the blast radius?
  5. Find the research question — what don't we understand about this problem that, if we understood it, would change the answer? What experiment would be most informative?

Read the full file on GitHub · 87 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. 8d ago First seen · 87 lines · 34 tokens per session scan A cec4ceac2fce

Subscribe to this mod's changes

council-sutskever is an agent published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,123 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to council-sutskever, differing in 17 lines, and is treated as a copy.