atrisCodebase intelligence — generates structured navigation maps with file:line references so agents stop re-scanning the same files every session. Use when exploring code, answering "where is X?", or onboarding to a new codebase.
Install via ClawdBot CLI:
clawdbot install keshav55/atrisMaintain a structured map of the codebase with exact file:line references. One scan, permanent knowledge. Saves 80-95% of tokens on code exploration.
atris/MAP.md as the single navigation index.Before searching for anything in the codebase:
atris/MAP.mdrg, then add the result to MAP.mdThe map gets smarter every time you use it. Never let a discovery go unrecorded.
If atris/MAP.md doesn't exist, generate it:
atris/ folder in the project rootatris/MAP.mdIf atris/MAP.md already exists, use it. Regenerate only if the user requests it or the map is clearly stale (references missing files, line numbers way off).
Skip: node_modules, .git, dist, build, vendor, pycache, .venv, .env, .key, .pem, credentials, secrets*
Use ripgrep to extract structure:
# Key definitions
rg "^(export|function|class|const|def |async def |router\.|app\.|@app\.)" --line-number -g "!node_modules" -g "!.git" -g "!dist" -g "!.env*"
# Route definitions
rg "(get|post|put|delete|patch)\s*\(" --line-number -g "*.ts" -g "*.js" -g "*.py"
# Entry points
rg "listen|createServer|app\.start|if __name__" --line-number# MAP.md — [Project Name] Navigation Guide
> Generated by Atris | Last updated: YYYY-MM-DD
## Quick Reference
rg "functionName" path/to/file.ext # Description (line N)
rg "className" path/to/file.ext # Description (line N)Extract the top 15-25 most important symbols: entry points, exports, route handlers, main classes, config loaders.
Group code by what it does. Every reference includes exact file path and line numbers.
### Feature: User Authentication
**Purpose:** Login, registration, token management
- **Entry:** `src/auth/login.ts:45-89` (handleLogin)
- **Validation:** `src/auth/validate.ts:12-67` (validateToken)
- **Model:** `src/models/user.ts:8-34` (User schema)
- **Routes:** `src/routes/auth.ts:5-28` (POST /login, POST /register)Group by cross-cutting patterns (error handling, logging, auth middleware, etc).
Flag high-impact files with why they matter and key functions with line numbers.
How execution flows — dev server startup, request lifecycle, build pipeline.
Update MAP.md surgically when the codebase changes:
Small updates, not full regeneration. The map evolves with the code.
Generated Mar 1, 2026
When a new developer joins a team, they need to quickly understand the codebase structure. Atris provides a structured navigation map that helps them locate key functions, classes, and entry points without repeatedly scanning files, reducing onboarding time by providing immediate file:line references.
When debugging or fixing issues, developers often need to trace through code to find relevant functions or modules. Atris allows them to check the map first to locate error handlers, validation logic, or specific route handlers directly, avoiding redundant searches and saving token usage during investigation sessions.
Before implementing new features, developers need to understand existing code organization and dependencies. Atris helps by grouping code by feature or concern, showing authentication modules, routing structures, and critical files with exact line numbers, enabling efficient planning without re-scanning the entire repository.
When working with older or poorly documented codebases, teams struggle to navigate unfamiliar structures. Atris generates a persistent map that captures key symbols and groupings, providing a living documentation index that evolves with updates, making legacy systems more accessible and maintainable over time.
During code reviews, reviewers need to quickly locate changed code in context. Atris offers a map with by-feature and by-concern groupings, allowing reviewers to see related files and functions at specific lines, streamlining the review process and ensuring thorough understanding of modifications.
Offer Atris as a cloud-based service with tiered plans based on repository size, team size, and advanced features like automated map updates or integration with CI/CD pipelines. Revenue comes from monthly or annual subscriptions, targeting development teams seeking token optimization and navigation efficiency.
Sell perpetual licenses or annual enterprise agreements to large organizations, including customization, on-premise deployment, and dedicated support. This model caters to companies with strict security requirements or complex codebases needing tailored integration with existing developer tools and workflows.
Provide a free version with basic map generation for individual developers or small teams, then charge for advanced capabilities like AI-assisted updates, team collaboration features, or priority support. This approach builds a user base while monetizing power users and organizations needing enhanced functionality.
💬 Integration Tip
Install ripgrep (rg) as a prerequisite, then integrate Atris into your development workflow by checking the map before any code search to maximize token savings and maintain map freshness with surgical updates.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
Perform a comprehensive read-only security audit of Clawdbot's own configuration. This is a knowledge-based skill that teaches Clawdbot to identify hardening opportunities across the system. Use when user asks to "run security check", "audit clawdbot", "check security hardening", or "what vulnerabilities does my Clawdbot have". This skill uses Clawdbot's internal capabilities and file system access to inspect configuration, detect misconfigurations, and recommend remediations. It is designed to be extensible - new checks can be added by updating this skill's knowledge.
Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers, handling secrets, input validation, SQL injection prevention, XSS protection, or any security-related code review.
Security check for ClawHub skills powered by Koi. Query the Clawdex API before installing any skill to verify it's safe.
Scan Clawdbot and MCP skills for malware, spyware, crypto-miners, and malicious code patterns before you install them. Security audit tool that detects data exfiltration, system modification attempts, backdoors, and obfuscation techniques.