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/run-testsgit 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.00011 | $0.00635 |
| Opus 5 | $0.00005 | $0.00318 |
| Sonnet 5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
run-tests 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests
Run unit tests and/or integration tests for the nylas CLI.
This is the authoritative source for test commands. Other files reference this document.
Instructions
Unit Tests
Run all unit tests:
go test ./...
Run tests for specific package:
go test ./internal/cli/email/...
go test ./internal/cli/webhook/...
go test ./internal/domain/...
go test ./internal/adapters/nylas/...
Run with verbose output:
go test -v ./...
Run with coverage:
go test -cover ./...
go test -coverprofile=coverage.out ./...
go tool cover -html=coverage.out
Integration Tests
Integration tests require credentials. Set environment variables:
# Required
export NYLAS_API_KEY="your-api-key"
export NYLAS_GRANT_ID="your-grant-id"
export NYLAS_TEST_BINARY="$(pwd)/bin/nylas"
# For email send tests
export NYLAS_TEST_SEND_EMAIL="true" # Enable send email tests
export NYLAS_TEST_EMAIL="[email protected]" # Recipient for send tests
export NYLAS_TEST_CC_EMAIL="[email protected]" # CC recipient (optional)
# Optional - for destructive tests
export NYLAS_TEST_DELETE="true" # Enable delete tests (contacts, folders, webhooks, drafts, calendars)
export NYLAS_TEST_DELETE_MESSAGE="true" # Enable email message delete tests
Build binary first:
go build -o bin/nylas ./cmd/nylas
Run integration tests:
go test -tags=integration ./internal/cli/integration/...
Run specific integration test:
go test -tags=integration -v ./internal/cli/integration/... -run "TestCLI_EmailList"
Common Test Patterns
If tests fail, check:
- Build errors: Run
go build ./...first - Missing mocks: Update
mock.goif interface changed - API changes: Update expected values in tests
- Credentials: Ensure env vars are set for integration tests
After fixing, always run full test suite:
go build ./... && go test ./...
Make Targets (Recommended)
make ci-full # Complete CI pipeline with cleanup (RECOMMENDED)
make ci # Quick CI (no integration tests)
make test-unit # Unit tests only
make test-race # Unit tests with race detector
make test-integration # CLI integration tests
make test-coverage # Generate coverage report
make test-cleanup # Clean up test resources
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 · 102 lines · 11 tokens per session scan A f5cf1276232f
run-tests is a command published in the GitHub repository nylas/cli (68 stars, last pushed 13d ago), licensed MIT. It adds 11 tokens to every session and 635 once invoked, about $0.0001 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 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.