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/flipbit03/lineark/update-docsgit clone --depth 1 https://github.com/flipbit03/linearkWhat 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.00483 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
update-docs 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.
What it actually says
Review and update all project documentation to reflect the current codebase.
Documentation files to update (in order):
crates/lineark-sdk/README.md— SDK crate README (published to crates.io)crates/lineark/README.md— CLI crate README (published to crates.io)README.md— Top-level project README (GitHub landing page)
Steps:
- Read all three README files listed above.
- Read these source files to understand the current state of the codebase:
crates/lineark-sdk/src/field_selection.rs— GraphQLFields trait, FieldCompatiblecrates/lineark-sdk/src/lib.rs— public re-exportscrates/lineark-derive/src/lib.rs— derive macro capabilitiescrates/lineark/src/commands/mod.rs— CLI command listcrates/lineark/src/commands/viewer.rs— example of lean type with full_typecrates/lineark-sdk/src/generated/client_impl.rs— available query/mutation methods
- For each README, check that:
- Code examples compile against the current API (generic queries need turbofish or type inference)
- All available commands/methods are listed
- Feature descriptions match actual capabilities (e.g., compile-time validation, custom field selection, FullType constraints)
- The three READMEs are consistent with each other (don't contradict)
- Update each README with accurate information. Keep the existing structure and tone. Don't bloat — be concise.
- Run
cargo fmtif any code examples were changed. - Report what changed in each file.
Key things to verify are accurate:
- Query methods table (SDK README) — return types, generic signatures
- Mutation methods table (SDK README) — generic signatures
- CLI command table (top-level README + CLI README) — all subcommands listed
- Custom field selection examples —
#[graphql(full_type = X)],#[graphql(nested)]attributes - The
search_issuesreturn type isConnection<IssueSearchResult>, NOTConnection<Issue> - Mutations are generic:
client.issue_create::<Issue>(input)or with type inference
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 · 35 lines · 0 tokens per session scan A df09a364f71d
update-docs is a command published in the GitHub repository flipbit03/lineark (54 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 483 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
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
linear-curator-run
Run the curator — collect signals from configured signal sources and report.
linear-sync
Populate or refresh the Linear reference files (teams, projects, users, workflows).
linear-search
Search Linear issues by keyword, team, assignee, state, or priority.
linear-my-issues
List Linear issues assigned to you, grouped by state.