rem-page-person

rem-page-person is a skill for Claude Code, Codex from openonion/connectonion. It costs 25 tokens per session (1,486 once invoked), scanned A, original, Apache-2.0.

A rule set for writing a consistent page about one person in a relationship notebook. It defines the sections, labels, evidence rules, and handling of missing information.

In plain words
What is it for?
Use it when creating or updating a person's page from supplied messages and other material. It helps record contact details, relationship history, sources, and uncertainties.
Why use it?
It prevents different stages from producing incomplete or differently shaped pages. It also keeps unsupported facts out of the notebook.

Skill for Claude CodeCodex

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

Good fit Use it when creating or updating a person's page from supplied messages and other material. It helps record contact details, relationship history, sources, and uncertainties.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openonion/connectonion/rem-page-person
About the project

ConnectOnion is an open-source, template-first toolkit for building, debugging, deploying, and operating AI agents. Developers use its command-line tools and Python runtime to create agents, add tools, connect services, deploy them, and make them callable by other agents, while the catalogue entries are related agents, skills, and instructions.

openonion/connectonion · 1,497 stars · on GitHub · docs.connectonion.com

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 openonion/connectonion --skill rem-page-person
Clone the repo
git clone --depth 1 https://github.com/openonion/connectonion

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 rem-page-person

README.md
[![agentmods](https://agentmods.dev/badge/skills/openonion/connectonion/rem-page-person/github.svg)](https://agentmods.dev/skills/openonion/connectonion/rem-page-person)
Your own site
<a href="https://agentmods.dev/skills/openonion/connectonion/rem-page-person"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/rem-page-person/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 rem-page-person

Your own site · 80×15
<a href="https://agentmods.dev/skills/openonion/connectonion/rem-page-person"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/rem-page-person.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,486 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 original No closer match found 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.00025 $0.01486
Opus 5.5 $0.00010 $0.00594
Sonnet 5.5 $0.00005 $0.00297
Haiku 4.5 $0.00003 $0.00149

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

Security

Grade A, and why

rem-page-person 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 yesterday.

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.

connectonion/useful_skills/rem-page-person/SKILL.md · 118 lines

How it starts

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

A person's page

Read supplied page/material. Write, check, fix once, stop; use this format.

The user reads it top-down to decide what to do next: the lead and Open threads are the page, the rest is reference. Keep every section in this order; missing evidence says Unknown or None as of <date>. Every factual sentence cites [n] into Sources. Placeholders are not evidence.

# <observed name>

<lead>. Last contact: <date>.

## Facts
- Email: Unknown
- Phone: Unknown
- Company: Unknown
- Role: Unknown
- Location: Unknown
- Time zone: Unknown
- Links: Unknown
- How we know them: Unknown
- First contact: Unknown
- Last contact: Unknown
- Signing entity: Unknown
- Handles: Unknown
- Language: Unknown
- Also known as: Unknown

## Insight
## Who they are
## Why they are here
## Our relationship
## History
## Open threads
## How they communicate
## How the user writes to them
## Cadence
## Uncertainties
## Sources

Rules:

  • Lead: three cited sentences, then Last contact: <date>, <channel>. (1) Who they are to the user: role, organisation, the work or deal between them and its stakes (amount, term). (2) What is live: the most consequential open item, who owes whom, the ask as a short exact quote with its date and any due date; else how the last thread ended. (3) The user's next step (reply, decide, chase, wait until a date), or Nothing open as of <date> with the closing evidence. Never open on a gap or a doubt.
  • One voice: the owner is the user in every sentence, never their name, you or we.
  • Facts is data, written first. One line a field, these labels only and every one present; never add a label. A missing value is exactly Unknown. Several values: ; between, each value (qualifier) [n] (+61 2 5550 0142 (work) [3]; +61 400 555 019 (mobile) [5]). Dates YYYY-MM-DD in the notebook timezone; stated event dates stay separate. Every value is cited except Email, Handles, Also known as. A contact detail never goes in a sentence instead of its field. Links: LinkedIn or a site. How we know them: who introduced whom, or the first thread.
  • Insight is 2–4 cited bullets of at most 30 words, each starting Now:, Changed:, At stake: or Pattern:: what reading the threads one by one would not show: what moved, what is at risk, a pattern over time (reply speed, topics, who chases whom). Never a copy of the lead or an open thread; never generic ("key stakeholder"); a single thread: - Unknown.
  • Language: the language they write to the user in.
  • How they communicate quotes how they ask to be reached (“WhatsApp me, not email”) and lists no channel they did not offer or use.
  • Company needs stated employment; a student or mailbox domain proves none (Unknown).
  • Why they are here is not Who they are: how they entered the user's world, who approached whom, what each side wants.
  • Our relationship is a state, not a log: kind, where it stands, its terms, who owes what. A term (amount, ratio, date, condition) is quoted with its date: “<exact words>” (YYYY-MM-DD) [n]. Keep each local link with its citations and privacy markers. Separate events, separate lines.
  • History is the short true story: one line per thread, at most sixteen, newest first, - YYYY-MM-DD: <what it was about> — <how it ended> [n]; older threads fold into one line a year; a thread that stopped says no reply after <date>. Not a send or a newsletter.
  • Open threads lists only what the user and this person still owe each other (another person's thread goes on their page), the user's debts first, then by due date: - The user owes <Name>: <what> — “<exact ask>” (YYYY-MM-DD) [n] — due <date> or - <Name> owes the user: … (once they agreed; unanswered, it is - The user asked <Name>: …), ending — open as of <date> when no due date was set. A later reply, a delivered item or a passed event date closes a thread: it moves to History. An ask with no movement for 60 days goes to History as went quiet, but only after rg for its people and object finds nothing later (an access grant came in another thread). Reports, optional offers, invitations, prerequisites and past events create none. Keep an explicit due date and any permission to proceed without a reply. Closure: Nothing open as of <date>.
  • Say each thing once, plainly. A fact lives in one section; the lead and Insight point to it. Status is a dated fact (no reply since 2026-10-12), never "is not established", "unconfirmed" or "in the supplied mail". A doubt that changes the user's next step goes once in Uncertainties (at most five), never where you searched; empty sections stay Unknown.
  • Keep what the map already knew. Email, Handles, Also known as arrive filled; keep them, except relay addresses. Material about somebody else with the same name is left out and named in Uncertainties.
  • Say their name or "they"; "he"/"she" only where their own words show it.
  • Sources: - [n] <source id> — <date>; claims stay in sentences. Never an assistant's memory file. List only cited sources.

Read the full file on GitHub · 118 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. yesterday Changed · +6 lines dd906c9ad55b
  2. 6d ago Changed a94d9e6ab52c
  3. 7d ago Changed · +1 lines d5fc5b59c4e8
  4. 14d ago Changed · +2 lines · -31 tokens per session 50b686a1943b
  5. 15d ago Changed · -19 lines 792c7dea0d45
  6. 16d ago Changed · +5 lines 6159204390a4
  7. 17d ago First seen · 123 lines · 56 tokens per session scan A 424b5b261d19

Subscribe to this mod's changes

rem-page-person is a skill published in the GitHub repository openonion/connectonion (1,497 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,486 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-30.