SiftStack: Instructions file for Claude Code

CLAUDE.md

SiftStack CLAUDE.md is an instructions file for Claude Code from DataSift-Ty-Personal/SiftStack. It costs 20,414 tokens per session, scanned A, original, MIT.

A repository-specific instruction file for SiftStack, a full-stack platform for running a real-estate investing business. It describes the project, setup, commands, and major workflows.

In plain words
What is it for?
Use it when developing, setting up, or troubleshooting SiftStack and its data collection, property analysis, market research, CRM, and lead-management workflows.
Why use it?
It gives a coding agent the context needed to work in this particular codebase without guessing how the project is organised or run.

Instructions file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is DataSift-Ty-Personal/SiftStack's own configuration. It tells Claude Code how to work on SiftStack itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SiftStack configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DataSift-Ty-Personal/SiftStack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/DataSift-Ty-Personal/SiftStack/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/DataSift-Ty-Personal/SiftStack

Made for: Claude Code.

Wrote 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.

agentmods badge for SiftStack CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/datasift-ty-personal/siftstack/claude-md/github.svg)](https://agentmods.dev/instructions/datasift-ty-personal/siftstack/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/datasift-ty-personal/siftstack/claude-md"><img src="https://agentmods.dev/badge/instructions/datasift-ty-personal/siftstack/claude-md/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.

agentmods 80×15 button for SiftStack CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/datasift-ty-personal/siftstack/claude-md"><img src="https://agentmods.dev/badge/instructions/datasift-ty-personal/siftstack/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20,414 This file is loaded in full into every session.
When invoked 20,414 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.20414 $0.20414
Opus 5.5 $0.08166 $0.08166
Sonnet 5.5 $0.04083 $0.04083
Haiku 4.5 $0.02041 $0.02041

Measured yesterday against content hash 6cf78b354f37, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

SiftStack CLAUDE.md 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.

CLAUDE.md · 663 lines

How it starts

The opening of the file, as written. The whole thing — 663 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md: SiftStack developer guide

This file guides Claude Code and developers working on SiftStack. It covers what the system is, how the repo is laid out, how to run, test and deploy each part, and the API contracts and traps that cost real time to find. The skill library's install guide is README.md; vendor contracts in depth are in docs/api/.

What SiftStack is

A real estate investing operations platform built around the DataSift.ai CRM (formerly REISift; app at app.reisift.io, API at apiv2.reisift.io). It covers the lead lifecycle end to end:

  • Acquisition: county public-notice scraping (foreclosure, probate, tax sale, tax delinquent), scanned PDF and courthouse-photo import, county recorder and condemnation sources.
  • Enrichment: address standardization, property data, county tax, obituary and heir research, skip trace, phone scoring.
  • CRM automation: API upload into DataSift, presets and sequences, an account blueprint cloner, a sold-property guard.
  • Deal analysis: comps, rehab, offer sheet, post-walkthrough package, dispo buyers, lender package.
  • The agents brain: four Claude "employees" in Slack plus an autopilot that runs the prospecting lifecycle stage by stage.
  • Outreach: a two-way SMS agent, Smarter Contact campaigns, cold email, direct mail.
  • The skill library: Claude skills shipped as a Claude Code plugin marketplace.

Python 3.12, flat modules under src/ (the import root, not a package), three Fly.io apps with SQLite on volumes, GitHub Actions for CI and outside watchdogs.

Ground rules

  1. The repo is public. Never commit keys, tokens, session or cookie files, county records naming people, recordings, vendor JS bundles or seller data. output/, logs/, .env, *_state.json, cookies.json, config/sms_*.json are gitignored for this reason. Read git status before every commit.
  2. Dry by default. Anything that writes to DataSift, pays a vendor or contacts a person is a plan unless given --commit; account-wide tools also need an env switch (*_ALLOW=1). New code keeps that contract.
  3. One record first. Before a batch write, write one record, read it back, compare. Most DataSift and vendor failures return a success status.
  4. A filter is proven by a count delta. DataSift and SiftMap silently ignore unknown filter keys. Count with and without the key before trusting it; acceptance proves nothing.
  5. Zero is a failure. A run with zero notices, zero records or zero matches exits non-zero or says so. Never infer success from the absence of an error or of challenge markup.
  6. Persist "handled" only after the downstream write succeeded (seen ids, ledgers, done-files), so an aborted run retries instead of skipping work forever.
  7. No silent degradation. A bare except that turns a 401 or 429 into "no data" is a bug. Count errors, retry transient ones, fail the phase past a threshold.
  8. Never fabricate. A research claim carries a URL it actually opened and a verbatim quote; a value with no source is Unknown. A wrong name or number reaches a real person.
  9. No em dash or en dash characters anywhere: code, docs, copy, commit messages. CI rejects them in docs/**/*.md and README.md. Number ranges use a plain hyphen.
  10. Read large files by range. Several modules exceed 50 KB (datasift_uploader.py, post_walkthrough.py, land_market.py, agents/autopilot/kpitracker.py, agents/autopilot/stages.py, sms_agent/selftest.py). Grep for the symbol, then read the lines around it.
  11. A stage verified only on a workstation is not verified. After a deploy, run each changed stage once on the box: datacenter egress, missing files and missing secrets only show up there.

Read the full file on GitHub · 663 lines

Changes

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.

  1. yesterday Changed · -186 lines · -11,937 tokens per session 6cf78b354f37
  2. 2mo ago First seen · 849 lines · 32,351 tokens per session scan A 2be6a80d1096

Subscribe to this mod's changes

SiftStack CLAUDE.md is an instructions file published in the GitHub repository DataSift-Ty-Personal/SiftStack (0 stars, last pushed yesterday), licensed MIT. It adds 20,414 tokens to every session, about $0.0817 per session on Opus 5.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.

Related

SiftStack CLAUDE.md compared with instructions from other repositories

SiftStack CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
SiftStack CLAUDE.mdDataSift-Ty-Personal/SiftStackInstructions file0yesterdayMITA20,414Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file196ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file144ktodayMITA8,130Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file196ktodayMITA5,685GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file150ktodayMITA4,680Codex, OpenCode
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file284ktodayMITA4,342Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file196ktodayMITA3,153GitHub Copilot