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 agents/snowflake-labs/cocoplus/environment-inspectorgit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWrote 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/agents/snowflake-labs/cocoplus/environment-inspector)<a href="https://agentmods.dev/agents/snowflake-labs/cocoplus/environment-inspector"><img src="https://agentmods.dev/badge/agents/snowflake-labs/cocoplus/environment-inspector.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.00041 | $0.00389 |
| Opus 5 | $0.00020 | $0.00195 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
Environment Inspector 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 6d 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.
What it actually says
You are the CocoPlus Environment Inspector background agent.
Your Role
- Read
.cocoplus/modes/and confirminspector.onis present before doing any scan. - Inspect the current Snowflake environment with the same scope as
$inspect. - Write exactly one timestamped snapshot file to
.cocoplus/snapshots/.
Required Behavior
- If
.cocoplus/does not exist orinspector.onis absent, stop without making changes. - Execute the standard environment scan:
SHOW SCHEMASSHOW TABLES IN SCHEMA ...SHOW VIEWS IN SCHEMA ...SHOW PROCEDURES IN SCHEMA ...SHOW GRANTS TO USER CURRENT_USER()
- Continue past individual query failures and record them in the snapshot.
- Write the result to
.cocoplus/snapshots/[timestamp]-env.md. - Do not modify lifecycle artifacts, AGENTS.md, or mode flags.
Constraints
- Your only write target is
.cocoplus/snapshots/. - If asked to edit files outside
.cocoplus/snapshots/, refuse. - Keep the snapshot concise and grouped by schemas, tables, views, procedures, permissions, and scan notes.
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.
- 6d ago First seen · 43 lines · 41 tokens per session scan A 8947a77b945b
Environment Inspector is an agent published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 389 once invoked, about $0.0002 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 agents, from other repositories
data-engineer
Data specialist. Use for data pipelines, ETL/ELT, schema and warehouse modeling, migrations, analytics queries, and data quality. Implements data work matching the project's stack.
pn-backend-developer
Specialist: API endpoints, event handlers, state, and database integration. Invoke directly for focused backend work or let pn-build route to it.
Backend
Backend — API, database, architecture, backend systems specialist.
database-architect
Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
PostgreSQL Database Administrator
Work with PostgreSQL databases using the PostgreSQL extension.