Let Claude Code run a sky camera through an MCP server that carries its own rules

What you end up with

The reusable idea is to put the rules where the agent cannot edit them.

What you get

• A plain-language summary of the workflow
• A fill-in prompt template
• What to watch out for
• A link to the original source

Who it is for

Builders who already use AI agents and want a proven workflow they can copy into their own project.

Works with

Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.

Tools needed

Cost to run: Free with the agent plan you already use.
Time to result: One working session

How it works

1. List the actions your device or app allows and mark each one read, wri

   List the actions your device or app allows and mark each one read, write or destructive

   Expected: Done before you move to the next step.

2. Wrap them in a small MCP server and return raw data, not verdicts

   Wrap them in a small MCP server and return raw data, not verdicts

   Expected: Done before you move to the next step.

3. Enforce the rules in the server: keys cannot create keys, deletes need

   Enforce the rules in the server: keys cannot create keys, deletes need preview then confirm, stale edits fail

   Expected: Done before you move to the next step.

4. Bundle two or three skill files with the server that explain the safe

   Bundle two or three skill files with the server that explain the safe way to do common jobs

   Expected: Done before you move to the next step.

5. Retrain or tune only on examples a person approved, and measure false

   Retrain or tune only on examples a person approved, and measure false alarms before and after

   Expected: Done before you move to the next step.

Sample prompt from the pack

Apply this workflow to [your project]:
1. List the actions your device or app allows and mark each one read, write or destructive
2. Wrap them in a small MCP server and return raw data, not verdicts
3. Enforce the rules in the server: keys cannot create keys, deletes need preview then confirm, stale edits fail
4. Bundle two or three skill files with the server that explain the safe way to do common jobs
5. Retrain or tune only on examples a person approved, and measure false alarms before and after
Stop and ask me before anything irreversible: deploys, payments, sends or deletes.

Free preview of the file

# Let Claude Code run a sky camera through an MCP server that carries its own rules

PaperChase agent use case (free feed entry), version 1.0. Source: [u/Terrible_Award_2124 on r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/comments/1xfqc9x/i_built_an_open_source_sky_camera_that_claude/), 2026-10-26.

## What they did

The builder made an all-sky camera that watches for meteors and wired it to Claude Code with an MCP server. The server comes with its own skills (build a workflow, find detections, verify changes), so any agent that connects learns how to use it the right way. Guardrails live in the server: no API key can mint new keys, deletes show a preview and need a confirm, and edits based on stale data are rejected. Claude then retrained the detector on detections the owner had approved, and the author reports star false alarms dropping from about half of all alerts to 7% while still catching about 90% of meteors.

## Worth knowing

The reusable idea is to put the rules where the agent cannot edit them. Prompts and instruction files can be ignored or rewritten, but a server that refuses a stale edit or an unconfirmed delete cannot. Bundling skills with the server also means you do not have to re-explain the tool in every project. Accuracy numbers are the author's own.

Worth knowing

• The reusable idea is to put the rules where the agent cannot edit them. Prompts and instruction files can be ignored or rewritten, but a server that refuses a stale edit or an unconfirmed delete cannot. Bundling skills with the server also means you do not have to re-explain the tool in every project. Accuracy numbers are the author's own.
• Figures are as reported by the original author and were not re-measured by us.

Details

Version 1.0 · Updated Oct 26, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms

Related

Prompt pack$14

AGENTS.md, CLAUDE.md and Cursor rules starter files

by PaperChaseWebb

Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules) and 8 prompts to write, trim and test your own.

Works withClaude CodeCodexCursorPlain .md

Vibe coding · Beginner · 20 min setup

Prompt pack$19

Ask-first rules for AI agents: hard nos, approval cards and a test set

by PaperChaseWebb

Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.

Works withClaude CodeCodexClaudeCursor+2Plain .md

Solo business · Beginner · 20 min setup