agentleFS
Sign inStart free
EskyeeEskyee/agentbot-opensource/skills/aeon-reg-monitor/SKILL.md

aeon-reg-monitor

Skill17 starsChanged 5 months agoMITView on GitHub

Track legislation, regulatory actions, and legal developments affecting prediction markets, crypto, and AI agents. Per item: stage (Rumor / Proposed / Comment / Final / Enforced), impact (kills the category / structural change / disclosure burden / noise), affected protocols by name, and a concrete operator action. Use as pre-trade context on legally-wrapped assets. Triggers: "what's happening in crypto reg", "track CFTC actions", "prediction market regulation", "new SEC rules", "AI agent compliance updates".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No editorial commentary. Cited facts only.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

aeon-reg-monitor

Regulatory intelligence for the stack pieces that get killed by a single rule change: prediction markets, agent-controlled wallets, stablecoins, MEV, AI compliance.

Sources

Federal Register, CFTC, SEC, FinCEN, EU Official Journal, ESMA, state AGs, court dockets via CourtListener. Industry counsel commentary as cross-reference only.

Output format

Items ranked by Stage × Impact. Final + Existential/High items lead. Rumor-stage items are included but visually separated.

FINAL × HIGH
  CFTC no-action sunset for sports-event contracts — Mar 31
  Affected: Kalshi sports markets, derived Polymarket clones
  Action: unwind positions resolving after Mar 31 OR confirm continued no-action
  Source: cftc.gov/PressReleases/...

COMMENT × HIGH
  Treasury proposed rule on stablecoin reserve composition
  Comment period closes Apr 14
  Affected: USDC issuer reserve mix (commercial paper exposure)
  Action: monitor; no immediate trade

RUMOR
  ESMA reportedly weighing MiCAR Article-12 application to prediction markets
  Single-source. Low confidence.
  Action: no action yet — confirmation watch.

Rules

  • Primary sources cited. "Reports indicate" without a filing or company post is rumor — flagged.
  • Stage and confidence paired — high-impact + low-confidence rumors are flagged as both.
  • Concrete operator action per item, or explicit "no action".
  • No editorial commentary. Cited facts only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free