geolectric

Boost Prompt

A prompt to boost your lazy "do this" prompts. Install with one of the buttons below.

Use

description
Beast Mode Dev

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

You are friendly, upbeat and helpful. You sprinkle in light humor where appropriate to keep the conversation engaging. Your personality is delightful and fun, but you are also serious about your work and getting things done.

Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
Select "Create new custom chat mode file"

description

tools

4.1 Beast Mode

changes

codebase

editFiles

extensions

fetch

findTestFiles

githubRepo

new

openSimpleBrowser

problems

readCellOutput

runCommands

runNotebooks

runTasks

runTests

search

searchResults

terminalLastCommand

terminalSelection

testFailure

updateUserPreferences

usages

vscodeAPI

Beast Mode v3 is out now: 👉 https://gist.github.com/burkeholland/88af0249c4b6aff3820bf37898c8bacf

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

Overview

Syncing an Ethereum node is largely reliant on latency and IOPS, I/O Per Second, of the storage. Budget SSDs will struggle to an extent, and some won't be able to sync at all. IOPS can roughly be used as proxy of / predictor for latency. Measuring latency directly is arguably better.

This document aims to snapshot some known good and known bad models.

The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.

For size, 4TB is a conservative choice which also supports a Fusaka "supernode". The smaller 2TB drive should last an Ethereum full node until at least sometime 2026, with [pre-merge history expiry](http


	# You'll need to pip install web3 for this, everything else should come as standard

	# Works as 'python snipertech.py {target-casesensitive} {sharesToBuy-1_to_9} {maximum_total_amount_in_ETH}
	# e.g. python snipertech.py functi0nZer0 1 0.4

	# Loops in ten second increments to try and buy your shares if they don't exist on FriendTech yet, then crashes out
	# Adjust loop length on line 86 if you want to be less frequent - if they already exist, it just buys and dies.

	import requests

	#! /bin/bash

	# -------- Config --------
	# WALLET_NAME should be the name of the wallet (chain-maind keys list)
	WALLET_NAME="Default"
	# If WALLET_ADDRESS is blank, it will try to pull your address. (chain-maind keys show ${WALLET_NAME} --address)
	# This is my address, so replace it with your own. Feel free to send me a murder of CROs.
	# NOTE: All transactions with my address will fail since you don't have my keys, of course.
	WALLET_ADDRESS="cro1ghlngrfrvjjf7r2h6ffpwaqcs630qxm509p2el"
	# VALIDATOR_IGNORE_REGEX is a Regular Expression that will ignore specific validators for re-delegating but

	#!/bin/bash -e

	# redelegate-cro.sh is a script that automatically claims all your delegation
	# rewards (across any number of validators) in a single transaction (assuming a
	# minimum reward threshold is met, to avoid spurious transactions). The rewards
	# are then automatically redelegated to the provided validator address, leaving
	# behind at least a 0.005 CRO buffer to ensure there is always enough for
	# regular transaction fees.
	#
	# The idea is that it is safe to run this script on a fixed cron schedule and

	<!DOCTYPE html>
	<html>
	<head>
	<title>Leaflet Demo</title>
	<meta charset="utf-8" />
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.7.3/leaflet.css" />

	<link href='http://fonts.googleapis.com/css?family=Open+Sans:600' rel='stylesheet' type='text/css'>
	<style>

	//NODE, MBTILES AND EXPRESS TILE SERVER WITH 200 CONCURRENT REQUESTS FOR 20seconds
	Target URL: http://localhost:7777/scene/tiles/15/29987/19801.png
	Completed requests: 7568
	Total errors: 0
	Total time: 20.001499538 s
	Requests per second: 378
	Total time: 20.001499538 s
	Percentage of the requests served within a certain time
	50% 518 ms
	90% 556 ms