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.
npx agentmods add skills/reflexioai/claude-smart/update-public-docsnpx skills add ReflexioAI/claude-smart --skill update-public-docsgit clone --depth 1 https://github.com/ReflexioAI/claude-smartWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00057 | $0.00825 |
| Opus 5 | $0.00028 | $0.00413 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
update-public-docs 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- update-public-docs — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Public Docs
Keep the public documentation at reflexio/public_docs/ in sync with the Python source code (client library, schemas, config models).
Source Files (authoritative)
Read these files to understand the current API surface:
reflexio/reflexio_client/reflexio/client.py— All public client methods (defines what's client-facing)reflexio/reflexio_commons/reflexio_commons/api_schema/service_schemas.py— Data models, enums, request/response schemasreflexio/reflexio_commons/reflexio_commons/api_schema/retriever_schema.py— Search/get request/response modelsreflexio/reflexio_commons/reflexio_commons/config_schema.py— Configuration models
Documentation Files (to update)
Read all MDX docs under reflexio/public_docs/content/docs/:
api-reference/client-*.mdx— Client method documentationapi-reference/schemas-*.mdx— Schema/model documentationconcepts/— Core concept pagesgetting-started/— Quickstart and setup guidesexamples/— Usage examples
Workflow
Step 1: Read All Sources
Read every source file listed above. Extract:
- All public methods from
ReflexioClient(name, parameters with types/defaults, return type, docstring) - All public Pydantic models used by those methods (field name, type, required/optional, default, description)
- All enum classes and their values
- All config model fields
Step 2: Read All Documentation
Read every MDX file under reflexio/public_docs/content/docs/.
Step 3: Compare and Update
For each doc category, compare source against docs and fix discrepancies:
Client methods (client-*.mdx):
- Every public method in
client.pymust be documented - Parameters: correct name, type, required/optional, default value
- Return type and response schema must match
- Remove docs for methods that no longer exist
Schema docs (schemas-*.mdx):
- Every field in each Pydantic model must appear in the documentation tables
- Field name, type, required/optional, default, and description must match source
- Remove docs for models/fields that no longer exist
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.
- 2d ago First seen · 99 lines · 57 tokens per session scan A 44f5aba9a3a0
update-public-docs is a skill published in the GitHub repository ReflexioAI/claude-smart (774 stars, last pushed 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 825 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
reflexio-embedded
Captures user facts and procedural corrections into .reflexio/ so the agent learns across sessions. Use when: (1) user states a preference, fact, config, or constraint; (2) user corrects the agent and confirms the fix with an explicit 'good'/'perfect' or by moving on without re-correcting for 1-2 turns; (3) at start…
reflexio-consolidate
Run a full-sweep consolidation over all .reflexio/ files — TTL sweep + n-way cluster merge. Use when the user asks to 'clean up reflexio', 'consolidate memory', 'deduplicate playbooks', or suspects drift across sessions.
reflexio
When to use: Always active. This skill is the contract between you and the reflexio cross-session memory plugin.
learn
When to use: The user wants immediate extraction of skills/preferences from the current session — e.g., after a major correction, before context compaction, or to test the loop.
clear-all
When to use: The user explicitly asks to delete all locally-stored skills/preferences. This is destructive and unrecoverable.
show
When to use: The user wants to see what reflexio currently knows about this project.