Borrowing it
Nothing to install: this file belongs to nylas/cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nylas/cli/main/.claude/commands/add-command/references/adapter-patterns.mdgit clone --depth 1 https://github.com/nylas/cliWrote 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/nylas/cli/adapter-patterns)<a href="https://agentmods.dev/commands/nylas/cli/adapter-patterns"><img src="https://agentmods.dev/badge/commands/nylas/cli/adapter-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nylas/cli/adapter-patterns"><img src="https://agentmods.dev/badge/commands/nylas/cli/adapter-patterns.svg" alt="Reviewed on agentmods" width="80" 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.01843 |
| Opus 5.5 | $0.00000 | $0.00737 |
| Sonnet 5.5 | $0.00000 | $0.00369 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
adapter-patterns 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 1mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapter Implementation Patterns
Reference patterns for implementing API methods in internal/adapters/nylas/.
File Structure
internal/adapters/nylas/
├── {resource}.go # Main implementation
├── {resource}_test.go # Unit tests
└── mock_{resource}.go # Mock implementation
List Method
// GetResources retrieves resources for a grant.
func (c *HTTPClient) GetResources(ctx context.Context, grantID string, params *domain.ResourceQueryParams) ([]domain.Resource, error) {
result, err := c.GetResourcesWithCursor(ctx, grantID, params)
if err != nil {
return nil, err
}
return result.Data, nil
}
// GetResourcesWithCursor retrieves resources with pagination cursor.
func (c *HTTPClient) GetResourcesWithCursor(ctx context.Context, grantID string, params *domain.ResourceQueryParams) (*domain.ResourceListResponse, error) {
queryURL := fmt.Sprintf("%s/v3/grants/%s/resources", c.baseURL, grantID)
queryParams := url.Values{}
if params != nil {
if params.Limit > 0 {
queryParams.Set("limit", strconv.Itoa(params.Limit))
}
if params.PageToken != "" {
queryParams.Set("page_token", params.PageToken)
}
// Add resource-specific params
}
if len(queryParams) > 0 {
queryURL += "?" + queryParams.Encode()
}
req, err := http.NewRequestWithContext(ctx, "GET", queryURL, nil)
if err != nil {
return nil, err
}
c.setAuthHeader(req)
resp, err := c.httpClient.Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
if resp.StatusCode != http.StatusOK {
return nil, c.handleErrorResponse(resp)
}
var result domain.ResourceListResponse
if err := json.NewDecoder(resp.Body).Decode(&result); err != nil {
return nil, err
}
return &result, nil
}
Get Single Method
// GetResource retrieves a single resource by ID.
func (c *HTTPClient) GetResource(ctx context.Context, grantID, resourceID string) (*domain.Resource, error) {
queryURL := fmt.Sprintf("%s/v3/grants/%s/resources/%s", c.baseURL, grantID, resourceID)
req, err := http.NewRequestWithContext(ctx, "GET", queryURL, nil)
if err != nil {
return nil, err
}
c.setAuthHeader(req)
resp, err := c.httpClient.Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
if resp.StatusCode != http.StatusOK {
return nil, c.handleErrorResponse(resp)
}
var result struct {
Data domain.Resource `json:"data"`
}
if err := json.NewDecoder(resp.Body).Decode(&result); err != nil {
return nil, err
}
return &result.Data, nil
}
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.
- 1mo ago First seen · 268 lines · 0 tokens per session scan A a2534adfa6c8
adapter-patterns is a command published in the GitHub repository nylas/cli (76 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,843 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
cabinet
Build a self-contained archive bundle for a single .eml — markdown, retained attachments, and source file in one directory.
dev
Dev stage — api-platform-implementer reads .claude/last-api-plan.md and implements (writes code, runs phpstan + phpunit + Infection on critical classes).
symfony-api-mcp
Expose API Platform 4.3 operations as MCP tools for AI agents (@experimental).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.