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 commands/markmhendrickson/neotoma/sync_env_from_1passwordgit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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.
[](https://agentmods.dev/commands/markmhendrickson/neotoma/sync_env_from_1password)<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/sync_env_from_1password"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/sync_env_from_1password.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02237 |
| Opus 5 | $0.00000 | $0.01118 |
| Sonnet 5 | $0.00000 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00224 |
Grade A, and why
sync_env_from_1password 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.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Environment Variables from 1Password
Syncs selected environment variables from 1Password into a local .env file.
Command
sync_env_from_1password
or
sync env from 1password
Purpose
This command executes the 1Password environment sync script, which:
- Reads environment variable mappings from parquet file via MCP server (or direct parquet read as fallback)
- Uses 1Password CLI (
op) to resolve each secret value - Updates the
.envfile with resolved values from 1Password - Creates a timestamped backup before modification
- Preserves unmanaged variables (variables not in 1Password mappings)
- Supports exclusion lists via configuration
Script Location:
scripts/op_sync_env_from_1password.py- Wrapper script (delegates to foundation)foundation/scripts/op_sync_env_from_1password.py- Foundation script (generalized, repository-agnostic)
When to Use
- After setting up a new repository or environment
- When environment variables need to be refreshed from 1Password
- After updating environment variable mappings in the parquet file
- When switching between environments (development/production)
- When
.envfile is missing or needs to be regenerated
Execution Instructions
Step 1: Verify Prerequisites
Check 1Password CLI authentication:
- Ensure
opCLI is installed - Verify you're signed in:
op whoamishould succeed - If not authenticated, sign in:
eval $(op signin)orop signin
Check Python environment:
- Ensure Python 3.9+ is available
- Verify required packages:
pandas,pyarrow(for fallback),mcp(for primary method) - Install if needed:
pip install pandas pyarrow mcp
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 · 322 lines · 0 tokens per session scan A ecbcfeb31c1e
sync_env_from_1password is a command published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,237 tokens. 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-03.
Other commands, from other repositories
tokenless-stats
Show Tokenless compression statistics.
perf
Run a performance audit on the Kernel platform.
status
Check the status of OpenClaw Machines development services.
supabase
Deploy and manage Supabase edge functions.
memory-review
Review contested and stale gitmem memories and propose resolutions.
remember
Save a durable fact or decision to gitmem memory.