What is service-lifecycle?

A reference for the Android VPN and proxy service lifecycle, including starting, stopping, restarting, policy handover, status, and telemetry. It maps the service shells to the runtime coordinators that perform the work.

Use it when changing VPN or proxy start and stop behaviour, handovers, remembered settings, runtime coordinators, or service status reporting.

Lifecycle behaviour is spread across several components, so changing the visible Android service alone can miss the code that actually controls the connection. The reference shows where each kind of change belongs.

How po4yka/RIPDPI configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to po4yka/RIPDPI. 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/po4yka/RIPDPI/main/.agents/skills/service-lifecycle/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/po4yka/RIPDPI

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/po4yka/ripdpi/service-lifecycle/github.svg)](https://agentmods.dev/skills/po4yka/ripdpi/service-lifecycle)

Your own site

<a href="https://agentmods.dev/skills/po4yka/ripdpi/service-lifecycle"><img src="https://agentmods.dev/badge/skills/po4yka/ripdpi/service-lifecycle/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/po4yka/ripdpi/service-lifecycle"><img src="https://agentmods.dev/badge/skills/po4yka/ripdpi/service-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,097 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.01097
Opus 5.5	$0.00017	$0.00439
Sonnet 5.5	$0.00009	$0.00219
Haiku 4.5	$0.00004	$0.00110

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

Security

Grade A, and why

service-lifecycle 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.

.agents/skills/service-lifecycle/SKILL.md · 113 lines

How it starts

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

Service Lifecycle

Overview

The Android services are thin shells now. Real lifecycle behavior lives in runtime coordinators plus ServiceStatusReporter, not in a single global app-state singleton.

Service work in this repo usually touches one or more of:

start/stop orchestration
remembered-policy replay
handover-triggered restarts
active-policy signature tracking
ServiceStateStore status, events, and telemetry
hidden first-seen-network quick_v1 diagnostics probes after successful handovers

Architecture

ServiceController.start(mode)
  -> START_ACTION / STOP_ACTION intent
  -> RipDpiVpnService or RipDpiProxyService
  -> ProxyServiceRuntimeCoordinator / VpnServiceRuntimeCoordinator
  -> ConnectionPolicyResolver
  -> proxy / tunnel runtime start-stop-restart
  -> ServiceStatusReporter
  -> ServiceStateStore

Key Components

Component	Location	Role
`ServiceController` / `DefaultServiceController`	`core/service/.../ServiceManager.kt`	App entry point for start/stop
`RipDpiVpnService`	`core/service/.../RipDpiVpnService.kt`	Android VPN service shell
`RipDpiProxyService`	`core/service/.../RipDpiProxyService.kt`	Android foreground proxy service shell
`BaseServiceRuntimeCoordinator`	`core/service/.../ServiceRuntimeCoordinator.kt`	Shared mutex, lifecycle state machine, stop/start/handover flow
`ProxyServiceRuntimeCoordinator`	`core/service/.../ProxyServiceRuntimeCoordinator.kt`	Proxy-mode runtime orchestration
`VpnServiceRuntimeCoordinator`	`core/service/.../VpnServiceRuntimeCoordinator.kt`	VPN-mode proxy+tunnel orchestration, resolver refresh, DNS failover
`ServiceStatusReporter`	`core/service/.../ServiceStatusReporter.kt`	Maps runtime changes into UI-facing status/events/telemetry
`ServiceStateStore`	`core/data/.../ServiceStateStore.kt`	Shared `StateFlow` / `SharedFlow` store observed by the app
`ConnectionPolicyResolver`	`core/service/.../ConnectionPolicyResolver.kt`	Resolves live or remembered policy for the current network
`NetworkHandoverMonitor`	`core/service/.../NetworkHandoverMonitor.kt`	Detects actionable network changes
`ActiveConnectionPolicyStore`	`core/service/.../ActiveConnectionPolicyStore.kt`	Persists active policy metadata for diagnostics and telemetry

Read the full file on GitHub · 113 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.

yesterday First seen · 113 lines · 43 tokens per session scan A 566d7ff6038c

Subscribe to this mod's changes

service-lifecycle is a skill published in the GitHub repository po4yka/RIPDPI (85 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 43 tokens to every session and 1,097 once invoked, about $0.0002 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-11-07.

Debugging Mobile android android-vpn anti-censorship censorship-circumvention deep-packet-inspection dns-over-https

service-lifecycle next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
service-lifecyclepo4yka/RIPDPI	Skill	85	yesterday	BSD-3-Clause	A	43	Claude Code, Codex
argent-react-native-app-workflowsoftware-mansion/argent	Skill	3.2k	today	Apache-2.0	A	46	Claude Code, Codex
argent-react-native-optimizationsoftware-mansion/argent	Skill	3.2k	today	Apache-2.0	A	71	Claude Code, Codex
argent-metro-debuggersoftware-mansion/argent	Skill	3.2k	today	Apache-2.0	A	104	Claude Code, Codex
argent-native-profilersoftware-mansion/argent	Skill	3.2k	today	Apache-2.0	A	37	Claude Code, Codex
compose-performancechrisbanes/skills	Skill	1.1k	2d ago	Apache-2.0	A	42	Claude Code
extract-apkniki914/zafiro	Skill	341	5d ago	MIT	A	105	Claude Code, Codex

RIPDPI: Skill for Claude Code