intercepting-mobile-traffic-with-burpsuite

intercepting-mobile-traffic-with-burpsuite is a cursor rule for Cursor from galyarderlabs/galyarder-framework. It costs 1 tokens per session (2,102 once invoked), scanned B, original, MIT.

The supplied information only identifies a set of workspace rules associated with intercepting mobile traffic using Burp Suite, a tool for inspecting network requests. It does not describe the add-on’s actual procedures.

In plain words
What is it for?
It appears intended for work involving mobile network-traffic inspection, but the supplied description does not support more specific claims.
Why use it?
There is not enough detail to state which mobile traffic or security tasks it supports beyond the topic named.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It appears intended for work involving mobile network-traffic inspection, but the supplied description does not support more specific claims.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite
Install

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.

Clone the repo
git clone --depth 1 https://github.com/galyarderlabs/galyarder-framework

Made for: Cursor.

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 intercepting-mobile-traffic-with-burpsuite

README.md
[![agentmods](https://agentmods.dev/badge/rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite/github.svg)](https://agentmods.dev/rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite)
Your own site
<a href="https://agentmods.dev/rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite"><img src="https://agentmods.dev/badge/rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite/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 intercepting-mobile-traffic-with-burpsuite

Your own site · 80×15
<a href="https://agentmods.dev/rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite"><img src="https://agentmods.dev/badge/rules/galyarderlabs/galyarder-framework/intercepting-mobile-traffic-with-burpsuite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00001 $0.02102
Opus 5 $0.00000 $0.01051
Sonnet 5 $0.00000 $0.00420
Haiku 4.5 $0.00000 $0.00210

Measured 9d ago against content hash f6da72aac81f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade B, and why

intercepting-mobile-traffic-with-burpsuite scanned grade B with 1 finding 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 9d ago.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

adb shell chmod 644 /system/etc/security/cacerts/$HASH.0
.cursor/rules/intercepting-mobile-traffic-with-burpsuite.mdc · 213 lines

How it starts

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

THE Agentic Company Framework GLOBAL PROTOCOLS (MANDATORY)

1. Token Economy: The RTK Prefix

The local environment is optimized with rtk (Rust Token Killer). Always use the rtk prefix for shell commands (e.g., rtk npm test) to minimize token consumption.

  • Example: rtk npm test, rtk git status, rtk ls -la.
  • Note: Never use raw bash commands unless rtk is unavailable.

2. Traceability: Linear is Law

No cognitive labor happens outside of a tracked ticket. You operate exclusively within the bounds of a project-scoped issue.

  • Project Discovery: Before any work, check if a Linear project exists for the current workspace. If not, CREATE it.
  • Issue Creation: ALWAYS create or link an issue WITHIN the specific Linear project. NEVER operate on 'No Project' issues.
  • Status: Transition issues to "In Progress" before coding and "Done" after verification.

3. Cognitive Integrity: Scratchpad Reasoning

Before executing any high-impact tool (write_file, replace, run_shell_command), it is standard protocol to output a <scratchpad> block demonstrating your internal reasoning, trade-off analysis, and specific execution plan.

4. Technical Integrity: The industry experts Principles

Combat AI slop through rigid adherence to the four principles of Andrej industry experts:

  1. Think Before Coding: Don't guess. If uncertain, STOP and ASK. State assumptions explicitly. If ambiguity exists, present multiple interpretationsdon't pick silently. Push back if a simpler approach exists.
  2. Simplicity First: Implement the minimum code that solves the problem. No speculative abstractions. If 200 lines could be 50, rewrite it. No "configurability" unless requested.
  3. Surgical Changes: Touch ONLY what is necessary. Every changed line must trace to the request. Don't "improve" adjacent code or refactor things that aren't broken. Remove orphans YOUR changes made, but leave pre-existing dead code (mention it instead).
  4. Goal-Driven Execution: Define success criteria via tests-first. Loop until verified.
    • Multi-step tasks MUST use this syntax:
      1. [Step] verify: [check]
      2. [Step] verify: [check]

Read the full file on GitHub · 213 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. 9d ago First seen · 213 lines · 1 tokens per session scan B f6da72aac81f

Subscribe to this mod's changes

intercepting-mobile-traffic-with-burpsuite is a cursor rule published in the GitHub repository galyarderlabs/galyarder-framework (24 stars, last pushed 1mo ago), licensed MIT. It adds 1 tokens to every session and 2,102 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.