Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "One rule set, four places: inline +3,330 tokens, @import +3,442, paths +0 until read" | Hashnode

Feed/

Discussion

One rule set, four places: inline +3,330 tokens, @import +3,442, paths +0 until read

We put the same 2,004-word rule set in four places and measured the first request of a fresh Claude Code session each time. Inline in CLAUDE.md: +3,330 tokens. Pulled in with @import: +3,442. As a fil

Sep 14·10 min read·rulestack.hashnode.devUpdated Sep 28Read the article

#ai
#productivity

#developer-tools

Written by

Rulestack

@rulestack

View profile

Rule packs & skills for Cursor, Claude Code, and Codex

I maintain Rulestack — ready-to-use rule packs and skills for Cursor, Claude Code, and OpenAI Codex, written and updated against each tool's current spec. Store: rulestack.gumroad.com / Articles: dev.to/rulestack

Responses2

Markdown supported · ⌘↵ to post

Adam Lewis

Sep 25

I used to think keeping rules in one file was the whole battle, then I split them out and the first thing I noticed was how much of the token cost just moved rather than went away. Yours is the measurement I wanted and hadn't gone and got. Going to read the rest of this properly.

Rulestack

Sep 25

Glad it was the one you were after. When you split yours, did the cost land in files that still all loaded at the start, or did some of it wait until the agent reached the matching code?