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/nylas/cli/auditgit clone --depth 1 https://github.com/nylas/cliWhat 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.00000 | $0.04217 |
| Opus 5 | $0.00000 | $0.02108 |
| Sonnet 5 | $0.00000 | $0.00843 |
| Haiku 4.5 | $0.00000 | $0.00422 |
Grade A, and why
audit 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.
How it starts
The opening of the file, as written. The whole thing — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Logging Guide
Complete guide to using Nylas CLI's audit logging for compliance, debugging, and tracking command execution across users and AI agents.
Key Feature: Audit logging captures who ran which commands, from what source (terminal, Claude Code, GitHub Actions, etc.), with full Nylas API traceability via request IDs.
Table of Contents
- Overview
- Quick Start
- Commands
- Invoker Identity Detection
- Filtering and Searching
- Configuration Options
- Storage and Retention
- Use Cases
- Troubleshooting
- FAQ
Overview
Audit logging records every CLI command execution with rich metadata for:
- Compliance - Track who accessed what data and when
- Debugging - Trace issues back to specific commands and API calls
- Security - Monitor for unauthorized access patterns
- AI Agent Tracking - Know when commands were run by Claude Code, GitHub Copilot, or other AI tools
What Gets Logged
| Field | Description | Example |
|---|---|---|
timestamp |
When the command was executed | 2026-02-05 10:30:00 |
command |
The CLI command run | email list |
args |
Sanitized command arguments | --limit 10 |
grant_id |
The Nylas grant (account) used | abc123... |
invoker |
Username who ran the command | alice, dependabot[bot] |
invoker_source |
Where the command originated | claude-code, terminal |
status |
Success or error | success |
duration |
How long it took | 190ms |
request_id |
Nylas API request ID for tracing | req_abc123 |
http_status |
HTTP response code | 200 |
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.
- yesterday First seen · 706 lines · 0 tokens per session scan A db4f7c101708
audit is a command published in the GitHub repository nylas/cli (68 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,217 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-08-30.
Other commands, from other repositories
create-pr
Create a pull request following the official template.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
numbers-to-excel
Convert a Numbers document to Excel.
briefing
Get a daily briefing of today's calendar events, reminders, and optional inbox context.
symfony-api-errors
Design API Platform 4.3 error handling — RFC 7807.
execute-plan
Execute an implementation plan methodically with TDD and continuous validation.