linear-cost-tuning
Optimizes Linear API usage to reduce costs and improve efficiency through effective management of API calls and rate limits.
Install this skill
Security score
The linear-cost-tuning skill was audited on May 12, 2026 and we found 21 security issues across 3 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 62 | requests: `${Math.round((this.requests / elapsedHours / 5000) * 100)}%`, |
Template literal with variable interpolation in command context
| 63 | complexity: `${Math.round((this.totalComplexity / elapsedHours / 250000) * 100)}%`, |
Template literal with variable interpolation in command context
| 145 | return coalesce(`team:${teamKey}`, async () => { |
Template literal with variable interpolation in command context
| 216 | console.log(`Synced ${synced} issues since ${lastSyncTime}`); |
Webhook reference - potential data exfiltration
| 35 | | Polling frequency | Wastes budget | Replace with webhooks | |
Webhook reference - potential data exfiltration
| 36 | | Webhook volume | Processing costs | Filter by event type and team | |
Webhook reference - potential data exfiltration
| 72 | ### Step 2: Replace Polling with Webhooks |
Webhook reference - potential data exfiltration
| 73 | The single biggest optimization. A polling loop checking every minute uses 1,440 requests/day. A webhook uses zero. |
Webhook reference - potential data exfiltration
| 86 | // GOOD: Webhook receives updates in real-time (0 requests for monitoring) |
Webhook reference - potential data exfiltration
| 87 | app.post("/webhooks/linear", express.raw({ type: "*/*" }), (req, res) => { |
Webhook reference - potential data exfiltration
| 162 | // Combined with webhook invalidation, even short TTLs |
Webhook reference - potential data exfiltration
| 166 | ### Step 6: Filter Webhook Events |
Webhook reference - potential data exfiltration
| 222 | - [ ] Replace all polling with webhooks |
Webhook reference - potential data exfiltration
| 225 | - [ ] Filter webhook events (skip bots, trivial updates, irrelevant teams) |
Webhook reference - potential data exfiltration
| 230 | - [ ] Cache teams/states/labels with webhook invalidation |
Webhook reference - potential data exfiltration
| 237 | | Stale cache data | TTL too long | Use webhook-driven invalidation | |
Webhook reference - potential data exfiltration
| 239 | | Webhook processing overload | Unfiltered events | Add type/team/field filtering | |
Webhook reference - potential data exfiltration
| 244 | - [Webhooks](https://linear.app/developers/webhooks) |
External URL reference
| 242 | - [Linear Rate Limiting](https://linear.app/developers/rate-limiting) |
External URL reference
| 243 | - [Linear Best Practices](https://linear.app/developers/graphql) |
External URL reference
| 244 | - [Webhooks](https://linear.app/developers/webhooks) |