bedrock: Skill for Claude Code

.agents/skills/loop-me/SKILL.md

loop-me is a skill for Claude Code, Codex from christopher-buss/bedrock. It costs 20 tokens per session (565 once invoked), scanned A, a copy of loop-me, MIT.

A guided questioning workflow that helps turn repeated activities into written workflow specifications. It asks questions in rounds and saves the resulting specifications in a workspace folder.

In plain words
What is it for?
Use it to define recurring workflows such as work routines or other repeated activities, with the goal of documenting how each should run.
Why use it?
It helps reveal missing requirements before building an automation. It also prevents assumptions about triggers, schedules, or other workflow parts when they have not been decided.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is christopher-buss/bedrock's own configuration. It tells Claude Code and Codex how to work on bedrock itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bedrock configures →

Reuse

Borrowing it

Nothing to install: this file belongs to christopher-buss/bedrock. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/christopher-buss/bedrock/main/.agents/skills/loop-me/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/christopher-buss/bedrock

Made for: Claude Code, Codex.

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 loop-me

README.md
[![agentmods](https://agentmods.dev/badge/skills/christopher-buss/bedrock/loop-me/github.svg)](https://agentmods.dev/skills/christopher-buss/bedrock/loop-me)
Your own site
<a href="https://agentmods.dev/skills/christopher-buss/bedrock/loop-me"><img src="https://agentmods.dev/badge/skills/christopher-buss/bedrock/loop-me/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 loop-me

Your own site · 80×15
<a href="https://agentmods.dev/skills/christopher-buss/bedrock/loop-me"><img src="https://agentmods.dev/badge/skills/christopher-buss/bedrock/loop-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 565 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 100% 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.00020 $0.00565
Opus 5.5 $0.00008 $0.00226
Sonnet 5.5 $0.00004 $0.00113
Haiku 4.5 $0.00002 $0.00056

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

Security

Grade A, and why

loop-me 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 5d 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

100% identical to loop-me — 0 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/skills/loop-me/SKILL.md · 33 lines

How it starts

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

Run a stateful /grilling session whose only output is workflow specs. Use the grilling discipline (relentless, a round of questions at a time, a recommended answer attached to each) aimed at the vocabulary and goal below. Create, edit, and delete specs as the grilling resolves things.

The loop lens

A loop is a recurring pattern in the user's life: their career, their week, their morning, a single repeated activity. Picturing a life as loops within loops reveals how predictable its activities really are, which is what makes them worth delegating. Use the lens to find loops worth specifying, and propose ones the user hasn't noticed.

A workflow is the spec of one loop, made real. You run a workflow on a loop: the loop is its running instantiation. Workflows live in workflows/*.md and are the source of truth.

Vocabulary

A shared language, reached for only when a workflow calls for it: never a checklist. Mandate nothing structural: a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does.

  • Trigger: what fires each run, an event (a new email, a new issue) or a schedule (every morning). Event-triggering is usually the more efficient.
  • Checkpoint: a human-in-the-loop point where the user is asked to verify or decide. Some workflows have none and run autonomously; some use no AI at all.
  • Push right: defer the checkpoint as far as it will go. Do maximal work before involving the human, so they are asked once, late, with everything prepared.
  • Brief: what a checkpoint presents, a tight, decision-ready summary (what was produced, why, and a link down to the asset itself), never the raw output. The user reads a brief, not a draft. Speed of review is imperative.

Definition of done

A workflow spec is done when an implementer agent could build it without asking a single question. Grill until then; nothing is done while a question remains.

The workspace

  • workflows/*.md: one spec per workflow.
  • NOTES.md: raw notes on the user's world, the tools they use, the channels they process, and their own terminology for both. When it is empty or thin, interview them about their world before specifying anything. Sharpen fuzzy terms into canonical ones as they surface, and record them here.

Read the full file on GitHub · 33 lines

Files

What ships with it

1 file 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.

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. 5d ago First seen · 33 lines · 20 tokens per session scan A e44d1cc3e760

Subscribe to this mod's changes

loop-me is a skill published in the GitHub repository christopher-buss/bedrock (19 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 565 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to loop-me, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

x-demand-radar

A radar for spotting fast-rising topics, tools, and projects on X, the social network formerly known as Twitter.

kennyzir/7deer_skills · 139 tokens

null-axiom-twitter

A writing tool that creates Twitter/X posts and threads in the Null Axiom persona, with a style aimed at indie developers and data-focused investigators. It can also draft replies to Twitter/X posts and send drafts to Feishu for review on a schedule.

kennyzir/7deer_skills · 129 tokens

roblox-site-architect

Orchestrate an evidence-backed seven-stage Roblox site growth pipeline from opportunity assessment through keyword research, source collection, site planning, SEO QA, freshness, and growth. Use when work needs staged artifacts and explicit handoffs rather than a one-click site generator.

kennyzir/7deer_skills · 57 tokens

site-keyword-research

A website keyword-research workflow that studies what people search for, expands related terms, and analyses competition in search results.

kennyzir/7deer_skills · 131 tokens

roblox-homepage-ranking-auditor

Audit a Roblox or game-site homepage against the RB Auto Golden Homepage model. Use when Codex must inspect a live homepage or repository, identify the primary player job and main engine, score structural ranking potential across eight dimensions, detect empty query modules, weak information gain, root/child intent…

kennyzir/7deer_skills · 120 tokens

roblox-hit-evaluator

Evaluate a Roblox game's 30-day breakout potential from public evidence with auditable scores, missing-data bounds, frozen forecasts, and outcome reviews.

kennyzir/7deer_skills · 34 tokens