messages-ops

messages-ops is a skill for Claude Code, Codex from nklofy/code-agent-skills. It costs 46 tokens per session (660 once invoked), scanned A, a copy of messages-ops, Apache-2.0.

A careful workflow for retrieving and inspecting live text messages, direct messages, or one-time codes. It identifies the message source and records which source or thread was actually checked.

In plain words
What is it for?
Use it to read local messages or DMs, find a recent login code, inspect a thread before replying, or document an authentication or access problem.
Why use it?
It prevents confusion between messaging surfaces and avoids claiming that a conversation or code was checked when access was blocked or the wrong source was used.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to read local messages or DMs, find a recent login code, inspect a thread before replying, or document an authentication or access problem.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nklofy/code-agent-skills/messages-ops
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.

Any agent
npx skills add nklofy/code-agent-skills --skill messages-ops
Clone the repo
git clone --depth 1 https://github.com/nklofy/code-agent-skills

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 messages-ops

README.md
[![agentmods](https://agentmods.dev/badge/skills/nklofy/code-agent-skills/messages-ops/github.svg)](https://agentmods.dev/skills/nklofy/code-agent-skills/messages-ops)
Your own site
<a href="https://agentmods.dev/skills/nklofy/code-agent-skills/messages-ops"><img src="https://agentmods.dev/badge/skills/nklofy/code-agent-skills/messages-ops/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 messages-ops

Your own site · 80×15
<a href="https://agentmods.dev/skills/nklofy/code-agent-skills/messages-ops"><img src="https://agentmods.dev/badge/skills/nklofy/code-agent-skills/messages-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 660 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 95% 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.00046 $0.00660
Opus 5 $0.00023 $0.00330
Sonnet 5 $0.00009 $0.00132
Haiku 4.5 $0.00005 $0.00066

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

Security

Grade A, and why

messages-ops 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 7d 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

95% identical to messages-ops — 3 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.

affaan-m-ECC/messages-ops/SKILL.md · 106 lines

How it starts

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

Messages Ops

Use this when the task is live-message retrieval: iMessage, DMs, recent one-time codes, or thread inspection before a follow-up.

This is not email work. If the dominant surface is a mailbox, use email-ops.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • email-ops when the message task is really mailbox work
  • connections-optimizer when the DM thread belongs to outbound network work
  • lead-intelligence when the live thread should inform targeting or warm-path outreach
  • knowledge-ops when the thread contents need to be captured into durable context

When to Use

  • user says "read my messages", "check texts", "look in DMs", or "find the code"
  • the task depends on a live thread or a recent code delivered to a local messaging surface
  • the user wants proof of which source or thread was inspected

Guardrails

  • resolve the source first:
    • local messages
    • X / social DM
    • another browser-gated message surface
  • do not claim a thread was checked without naming the source
  • do not improvise raw database access if a checked helper or standard path exists
  • if auth or MFA blocks the surface, report the exact blocker

Workflow

1. Resolve the exact thread

Before doing anything else, settle:

  • message surface
  • sender / recipient / service
  • time window
  • whether the task is retrieval, inspection, or prep for a reply

2. Read before drafting

If the task may turn into an outbound follow-up:

  • read the latest inbound
  • identify the open loop
  • then hand off to the correct outbound skill if needed

3. Handle codes as a focused retrieval task

For one-time codes:

  • search the recent local message window first
  • narrow by service or sender when possible
  • stop once the code is found or the focused search is exhausted

4. Report exact evidence

Return:

  • source used
  • thread or sender when possible
  • time window
  • exact status:
    • read
    • code-found
    • blocked
    • awaiting reply draft

Read the full file on GitHub · 106 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. 7d ago First seen · 106 lines · 46 tokens per session scan A c2036d3ff01f

Subscribe to this mod's changes

messages-ops is a skill published in the GitHub repository nklofy/code-agent-skills (18 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 660 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to messages-ops, differing in 3 lines, and is treated as a copy.